Crypto Exchange Solutions

DEX Development Timeline 2026: How Long Does It Take to Launch?

Oct 23, 2026 · 13 min read
In this article
Need Help?
Talk to Our Experts

Building a decentralized exchange (DEX) involves much more than writing smart contracts and connecting crypto wallets. The DEX development timeline depends on your trading model, blockchain network, feature scope, integrations and security testing. A focused DEX MVP may take around 6–12 weeks, while a complex custom platform with advanced trading features can take 3–6 months or longer.

Your development approach also affects the launch date. White-label DEX development reuses existing components to reduce the initial build, while custom DEX development gives you more control over trading logic, architecture and features.

Finishing the code, however, does not make a DEX ready for production. Testing, smart contract security reviews, fixes, liquidity preparation and deployment checks all need a place in the schedule. This guide explains how long each type of DEX usually takes, what happens at every stage and which factors can speed up or delay your launch.

How Long Does It Take to Build a Decentralized Exchange?

A decentralized exchange can take anywhere from a few weeks to several months to build. The range depends on how complex the platform is and how much existing technology can be reused.

DEX Development Timeline by Project Type

DEX project typeIndicative timelineTypical scope
White-label DEX3–8 weeksExisting platform components, branding, wallet connectivity, basic swaps
DEX MVP6–12 weeksCore trading features, liquidity functionality, wallet integration, testing
Custom DEX3–6 monthsCustom architecture, trading logic, interface and integrations
Advanced multi-chain DEX6–12+ monthsMultiple networks, cross-chain functionality, complex integrations, extensive security testing

These ranges are planning estimates, not guaranteed delivery times or verified industry averages. They assume clear requirements, an experienced development team and access to the resources the project needs.

Actual timelines also shift with component reuse, team size, audit requirements, fix time, liquidity arrangements and third-party dependencies.

DEX Development Timeline by Exchange Model

The development model decides how much must be built, configured, integrated and tested before launch.

White-Label DEX Development Timeline

A white-label DEX may take around 3–8 weeks to configure and prepare when the existing platform closely matches your requirements. Because core components are already available, developers focus on configuration rather than building every feature from scratch.

The work usually includes:

  • Reviewing the existing solution and confirming requirements
  • Customizing branding and the trading interface
  • Configuring the supported blockchain and wallets
  • Setting up token swaps and liquidity-related integrations
  • Testing transactions and checking deployment settings

The timeline grows if the platform needs heavy customization, extra blockchain networks or integrations that are not supported out of the box. Before handling real user funds, any white-label solution still needs code-quality checks, integration testing and a security review.

DEX MVP Development Timeline

DEX MVP development generally takes around 6–12 weeks, depending on feature scope and how much functionality can be reused. A minimum viable product focuses on the features needed to test the trading experience and collect feedback. A basic MVP may include:

  • Wallet connection
  • Token swaps on one selected blockchain
  • Basic liquidity pool functionality, where the trading model requires it
  • Token prices and transaction status
  • Essential error handling and user feedback
  • Automated testing and appropriate security reviews

Advanced analytics and cross-chain swaps can wait for later releases, but the core contracts still need strong security testing.

Custom DEX Development Timeline

Custom DEX development typically takes around 3–6 months for a moderately complex platform. Custom smart contracts, advanced trading functionality, multiple networks or specialized liquidity mechanisms can push it beyond six months.

The team defines the architecture, builds or adapts trading logic, creates the interface, integrates blockchain services and tests the full transaction flow.


Custom builds offer the most flexibility, but every new feature adds implementation and testing time. The overall timeline depends on the platform’s complexity, security requirements, and the number of features planned for launch.

How DEX Architecture Affects the Development Timeline

Two projects can both be called decentralized exchanges and still have very different schedules. The trading architecture is one of the main reasons. For a wider overview, read our DEX development guide.

DEX architectureMain development considerationsTimeline impact
AMM-based DEXLiquidity pools, swap calculations, fees, slippage, pool interactionsCan be relatively straightforward when established components fit the requirements
Order-book DEXOrder creation, cancellation, matching, settlement, order-state managementComplex matching and settlement increase engineering and testing effort
Multi-chain DEXNetwork-specific contracts, wallet support, cross-chain communication, failure handlingExtra networks and cross-chain execution add substantial integration and security work

An automated market maker (AMM) uses liquidity pools and pricing logic to facilitate swaps; established components keep the scope manageable.

An order-book DEX must manage orders and their execution. The design may use on-chain order handling, off-chain components or a hybrid approach, and that choice directly affects performance, complexity and testing.

A multi-chain DEX needs careful network planning. Supporting several networks independently is not the same as letting a single transaction move assets across chains. Cross-chain features add messaging, bridging, coordination and extra failure scenarios, so the interoperability design matters more than the number of chains.

DEX Development Stages and Their Estimated Duration

A DEX project typically moves through planning, design, development, integration, testing and launch preparation, much like the wider crypto exchange development process.

Development stageIndicative durationKey activities
Requirements and planning1–2 weeksConfirm trading model, scope, blockchain and launch goals
UI/UX design and architecture1–3 weeksDesign user flows and define technical architecture
Smart contract and frontend development3–8 weeksBuild or configure trading logic, contracts and interface
Blockchain and API integration1–3 weeksConnect wallets, blockchain services and external providers
Testing, security review and fixes2–4+ weeksValidate functionality, review contracts, fix and retest issues
Deployment and launch preparation1–2 weeksVerify configurations, deploy contracts, complete release checks

Added one after another, these stages total roughly 9–22 weeks. In practice many activities overlap, such as design with architecture planning or integration with frontend work, which is why a focused MVP can still launch within 6–12 weeks.

Requirements and Project Planning (1–2 weeks)

This stage defines what the exchange must do and sets the boundaries of the first release. The team agrees on the target blockchain, trading model, supported assets, core features, liquidity approach and required integrations. Security expectations and launch criteria should be set before implementation begins.

Clear requirements prevent costly rework later.

UI/UX Design and Technical Architecture (1–3 weeks)

Here the team designs user flows such as wallet connection, token selection, swap confirmation, slippage settings and error messages, and decides how smart contracts, the frontend and supporting services communicate.

Smart Contract and Frontend Development (3–8 weeks)

Developers build or configure the contracts and interface for the agreed scope. Smart contract work may include swap logic, liquidity pool interactions, fee calculations and access controls. Front-end work connects the interface to wallets and blockchain transactions.

Blockchain and Third-Party Integration (1–3 weeks)

The platform needs reliable connections to the chosen blockchain and any external services. These may include wallet providers, blockchain nodes or RPC services, token data, price feeds and indexing services. Not every DEX needs every integration.

Integration can overlap with frontend work, but missing API credentials or unsupported networks can delay testing.

Testing, Security Review and Bug Fixes (2–4+ weeks)

Testing checks how the exchange behaves under normal and unusual conditions. It can include unit tests, integration tests, transaction-flow tests and edge cases such as failed transactions or insufficient liquidity.

Smart contracts need special attention because vulnerabilities can put user funds at risk. Security work may include code review, automated analysis and an independent audit, and our guide to crypto exchange security covers the wider safeguards. An audit is not a simple final approval: if reviewers find issues, developers need time to fix them and verify the fixes.

Mainnet Deployment and Launch Preparation (1–2 weeks)

The final stage prepares the exchange for production. The team verifies contract configuration, wallet connectivity and essential transaction flows, and sets up monitoring and incident response. Launch only when your release criteria are met.

What Does a Realistic DEX Project Schedule Look Like?

A useful timeline shows dependencies and parallel work. Below is an illustrative 12-week plan for a focused, single-chain DEX MVP with compatible components and an independent audit. It is not a delivery guarantee.

PeriodMain workDependency or milestone
Weeks 1–2Confirm requirements, select architecture, finalize user flowsScope and technical decisions approved
Weeks 2–3Complete interface design and prepare development environmentsDesign overlaps with architecture finalization
Weeks 3–5Develop or configure contracts and frontendCore functionality built in stages
Weeks 4–6Integrate wallets and blockchain services; begin integration testingIntegration starts as components become available
Weeks 6–7Complete functional testing; freeze contract code for reviewContracts ready for the auditor
Weeks 7–10Independent security auditAuditor findings documented and prioritized
Weeks 10–11Fix findings and retestCritical issues verified as resolved
Weeks 11–12Verify deployment configuration and prepare launchRelease depends on security and functional acceptance

Overlapping design, architecture and integration work shortens the schedule compared with a strictly sequential plan. The audit and remediation, however, add roughly four to five weeks. Without an independent audit, the same project could fit the 6–8 week range, but only if lighter review methods are acceptable for the project’s risk level. Serious audit findings can stretch the plan further.

What Factors Affect the DEX Development Timeline?

FactorWhy it changes the schedule
Trading model and contract complexityCustom pricing, order execution or liquidity rules need more building and validation
Blockchain network and integrationsEach network adds deployments, wallet support and testing
Feature scope and customizationEvery extra feature adds design, development, integration and testing work
Security audits and remediationReview time depends on contract complexity, auditor availability and findings
Team experience and decision-makingFamiliarity and fast approvals prevent rework and idle time

Trading-model complexity and security remediation usually move the schedule the most, because custom logic and audit findings both create rework.

Can You Launch a DEX in 30 Days?

A limited DEX may be possible in 30 days, but only under narrow conditions. The most realistic case is a white-label DEX that already matches your requirements, with finalized scope and minimal customization. A 30-day launch should not be treated as a standard timeline for a production-ready custom exchange.

TimelineMain activities
Days 1–5Finalize scope, select the blockchain, confirm the technical approach
Days 6–12Configure existing components and customize the trading interface
Days 13–19Connect wallets and blockchain services; validate core swap functionality
Days 20–25Run functional testing, security checks and necessary fixes
Days 26–30Retest, verify deployment settings and prepare launch if release criteria are met

This plan assumes suitable components and no major issues. Original contract logic, complex integrations or an audit with remediation need more time, and the launch date should move rather than skip security checks.

How to Reduce DEX Development Time Without Compromising Security

The best way to shorten a DEX development timeline is to remove avoidable work, not to skip testing. Scope also drives budget, so read the crypto exchange development cost breakdown alongside your plan.

  • Prioritize launch-critical features. Build what users need first and schedule the rest for later phases.
  • Finalize the trading model early. Switching from AMM to order-book after development starts causes major rework.
  • Choose compatible components. Established libraries and frameworks save effort when they fit the requirements.
  • Start integration and testing early. Confirm wallet, blockchain and API needs upfront, and run automated tests throughout development.
  • Plan security reviews in advance. Agree the review scope early and leave room for fixes and retesting.
  • Control scope changes. Assess how each new request affects cost, dependencies and the launch date.

DEX Launch-Readiness Checklist

Before deploying to mainnet, confirm the following:

  • Smart contracts are tested against the intended transaction flows.
  • Required code reviews and security audits are complete.
  • Critical vulnerabilities are fixed and the fixes verified.
  • Wallet connectivity and transaction handling are tested.
  • Supported tokens, pool settings, fees and contract configurations are checked.
  • Blockchain and third-party integrations work as expected.
  • Liquidity arrangements are ready, where applicable.
  • Monitoring, incident response and maintenance responsibilities are defined.
  • Deployment details are verified and release criteria are agreed.

Adapt the checklist to your architecture and risk profile; it reduces oversights but cannot guarantee a system is free of vulnerabilities.

How to Choose a DEX Development Partner for Your Timeline

A good partner gives you more than a launch date. They should explain what will be delivered, which dependencies could cause delays and how testing and audits fit into the schedule. Experienced crypto exchange development teams usually document these assumptions upfront.

  • Relevant technical experience with your blockchain, smart contracts and trading model
  • A clear project plan with milestones for requirements, design, build, integration, testing and deployment
  • Transparent assumptions about reused components, custom development, audits and remediation time
  • A realistic change process for new features or shifting requirements
  • Post-launch support for monitoring, maintenance, bug fixes and upgrades

Be cautious of anyone who guarantees a production-ready DEX in an unusually short time without explaining scope or security.

Final Thoughts: Plan Your DEX Launch with Craitrix

The DEX development timeline depends on your trading model, architecture, feature scope, integrations and security requirements. White-label development supports a faster start, an MVP helps you validate a focused product, and custom or multi-chain platforms need more planning and engineering. Whichever route you choose, define the launch scope first and budget time for testing, audits and deployment.

Craitrix is a blockchain development company that delivers end-to-end decentralized exchange development services for businesses ready to launch their own trading platform. Whether you need a white-label DEX for a fast start, an MVP to test your idea or a custom cross-chain exchange, our team builds the platform around your goals and a realistic timeline. 

  • Choose the right DEX development approach for your business goals
  • Finalize the trading model, blockchain network and core features
  • Develop smart contracts, trading interfaces and blockchain integrations
  • Plan testing, security audits and mainnet deployment

What you can expect when you work with us:

  • A structured process covering planning, design, development, integration, testing and launch, as outlined above
  • Scope and timeline planned together before development starts
  • Security checks built into the schedule, not added at the end

Planning to launch a DEX? Connect with Craitrix to discuss your requirements, estimate your development timeline and create a roadmap for your project.

Frequently Asked Questions

Q1. How long does it take to develop a DEX from scratch?

Ans: A moderately complex custom DEX may take around 3–6 months. Advanced trading logic, multiple networks or complex liquidity mechanisms can extend that to six months or longer.

Q2. What is the typical white-label DEX development timeline?

Ans: A white-label DEX may take around 3–8 weeks when the platform meets your requirements. Heavy customization, extra networks, additional integrations or security findings can extend it.

Q3. How long does a Uniswap-style DEX take to build?

Ans: A basic AMM DEX built on suitable existing contract components may take roughly 6–10 weeks to reach a testable release, with an independent audit and fixes adding more time. Custom pool logic or extra networks need longer, and reused code still requires security testing.

Q4. Can a DEX MVP be launched in 6–8 weeks?

Ans: It may be possible with a limited feature set, finalized requirements and compatible components. A broader MVP usually needs 6–12 weeks, and custom contracts, complex integrations or audit remediation can add more.

Q5. How long does multi-chain DEX development take?

Ans: An advanced multi-chain DEX may take 6–12 months or longer, especially with cross-chain swaps or custom bridging.

Q6. Does a smart contract audit affect the DEX launch date?

Ans: Yes. An audit can add time depending on contract complexity, auditor availability, findings and the time needed to fix and retest issues. Plan the review early and never launch with unresolved critical vulnerabilities.

Ram Mohan MS

About the Author

Ram Mohan MS

Founder & CEO - Craitrix Technologies

Rammohan is the Founder & CEO of Craitrix Technologies, specializing in blockchain, Web3, and scalable enterprise solutions. With hands-on experience in delivering secure, high-performance digital platforms, he has guided startups and businesses through complex technology transformations. His expertise spans crypto exchange development, custom software, and digital innovation strategies. Rammohan regularly shares insights on emerging technologies, helping businesses make informed, future-ready decisions.

Ready to launch your own Blockchain venture? Start your journey with our expert team today.

Connect with Us

Let's talk about your project.

We’re here to help—share your thoughts or inquiries with us, and we’ll get back to you soon!

Person pointing
  • United States+1
  • United Kingdom+44
  • Afghanistan (‫افغانستان‬‎)+93
  • Albania (Shqipëri)+355
  • Algeria (‫الجزائر‬‎)+213
  • American Samoa+1
  • Andorra+376
  • Angola+244
  • Anguilla+1
  • Antigua and Barbuda+1
  • Argentina+54
  • Armenia (Հայաստան)+374
  • Aruba+297
  • Ascension Island+247
  • Australia+61
  • Austria (Österreich)+43
  • Azerbaijan (Azərbaycan)+994
  • Bahamas+1
  • Bahrain (‫البحرين‬‎)+973
  • Bangladesh (বাংলাদেশ)+880
  • Barbados+1
  • Belarus (Беларусь)+375
  • Belgium (België)+32
  • Belize+501
  • Benin (Bénin)+229
  • Bermuda+1
  • Bhutan (འབྲུག)+975
  • Bolivia+591
  • Bosnia and Herzegovina (Босна и Херцеговина)+387
  • Botswana+267
  • Brazil (Brasil)+55
  • British Indian Ocean Territory+246
  • British Virgin Islands+1
  • Brunei+673
  • Bulgaria (България)+359
  • Burkina Faso+226
  • Burundi (Uburundi)+257
  • Cambodia (កម្ពុជា)+855
  • Cameroon (Cameroun)+237
  • Canada+1
  • Cape Verde (Kabu Verdi)+238
  • Caribbean Netherlands+599
  • Cayman Islands+1
  • Central African Republic (République centrafricaine)+236
  • Chad (Tchad)+235
  • Chile+56
  • China (中国)+86
  • Christmas Island+61
  • Cocos (Keeling) Islands+61
  • Colombia+57
  • Comoros (‫جزر القمر‬‎)+269
  • Congo (DRC) (Jamhuri ya Kidemokrasia ya Kongo)+243
  • Congo (Republic) (Congo-Brazzaville)+242
  • Cook Islands+682
  • Costa Rica+506
  • Côte d’Ivoire+225
  • Croatia (Hrvatska)+385
  • Cuba+53
  • Curaçao+599
  • Cyprus (Κύπρος)+357
  • Czech Republic (Česká republika)+420
  • Denmark (Danmark)+45
  • Djibouti+253
  • Dominica+1
  • Dominican Republic (República Dominicana)+1
  • Ecuador+593
  • Egypt (‫مصر‬‎)+20
  • El Salvador+503
  • Equatorial Guinea (Guinea Ecuatorial)+240
  • Eritrea+291
  • Estonia (Eesti)+372
  • Eswatini+268
  • Ethiopia+251
  • Falkland Islands (Islas Malvinas)+500
  • Faroe Islands (Føroyar)+298
  • Fiji+679
  • Finland (Suomi)+358
  • France+33
  • French Guiana (Guyane française)+594
  • French Polynesia (Polynésie française)+689
  • Gabon+241
  • Gambia+220
  • Georgia (საქართველო)+995
  • Germany (Deutschland)+49
  • Ghana (Gaana)+233
  • Gibraltar+350
  • Greece (Ελλάδα)+30
  • Greenland (Kalaallit Nunaat)+299
  • Grenada+1
  • Guadeloupe+590
  • Guam+1
  • Guatemala+502
  • Guernsey+44
  • Guinea (Guinée)+224
  • Guinea-Bissau (Guiné Bissau)+245
  • Guyana+592
  • Haiti+509
  • Honduras+504
  • Hong Kong (香港)+852
  • Hungary (Magyarország)+36
  • Iceland (Ísland)+354
  • India (भारत)+91
  • Indonesia+62
  • Iran (‫ایران‬‎)+98
  • Iraq (‫العراق‬‎)+964
  • Ireland+353
  • Isle of Man+44
  • Israel (‫ישראל‬‎)+972
  • Italy (Italia)+39
  • Jamaica+1
  • Japan (日本)+81
  • Jersey+44
  • Jordan (‫الأردن‬‎)+962
  • Kazakhstan (Казахстан)+7
  • Kenya+254
  • Kiribati+686
  • Kosovo+383
  • Kuwait (‫الكويت‬‎)+965
  • Kyrgyzstan (Кыргызстан)+996
  • Laos (ລາວ)+856
  • Latvia (Latvija)+371
  • Lebanon (‫لبنان‬‎)+961
  • Lesotho+266
  • Liberia+231
  • Libya (‫ليبيا‬‎)+218
  • Liechtenstein+423
  • Lithuania (Lietuva)+370
  • Luxembourg+352
  • Macau (澳門)+853
  • Madagascar (Madagasikara)+261
  • Malawi+265
  • Malaysia+60
  • Maldives+960
  • Mali+223
  • Malta+356
  • Marshall Islands+692
  • Martinique+596
  • Mauritania (‫موريتانيا‬‎)+222
  • Mauritius (Moris)+230
  • Mayotte+262
  • Mexico (México)+52
  • Micronesia+691
  • Moldova (Republica Moldova)+373
  • Monaco+377
  • Mongolia (Монгол)+976
  • Montenegro (Crna Gora)+382
  • Montserrat+1
  • Morocco (‫المغرب‬‎)+212
  • Mozambique (Moçambique)+258
  • Myanmar (Burma) (မြန်မာ)+95
  • Namibia (Namibië)+264
  • Nauru+674
  • Nepal (नेपाल)+977
  • Netherlands (Nederland)+31
  • New Caledonia (Nouvelle-Calédonie)+687
  • New Zealand+64
  • Nicaragua+505
  • Niger (Nijar)+227
  • Nigeria+234
  • Niue+683
  • Norfolk Island+672
  • North Korea (조선 민주주의 인민 공화국)+850
  • North Macedonia (Северна Македонија)+389
  • Northern Mariana Islands+1
  • Norway (Norge)+47
  • Oman (‫عُمان‬‎)+968
  • Pakistan (‫پاکستان‬‎)+92
  • Palau+680
  • Palestine (‫فلسطين‬‎)+970
  • Panama (Panamá)+507
  • Papua New Guinea+675
  • Paraguay+595
  • Peru (Perú)+51
  • Philippines+63
  • Poland (Polska)+48
  • Portugal+351
  • Puerto Rico+1
  • Qatar (‫قطر‬‎)+974
  • Réunion (La Réunion)+262
  • Romania (România)+40
  • Russia (Россия)+7
  • Rwanda+250
  • Saint Barthélemy+590
  • Saint Helena+290
  • Saint Kitts and Nevis+1
  • Saint Lucia+1
  • Saint Martin (Saint-Martin (partie française))+590
  • Saint Pierre and Miquelon (Saint-Pierre-et-Miquelon)+508
  • Saint Vincent and the Grenadines+1
  • Samoa+685
  • San Marino+378
  • São Tomé and Príncipe (São Tomé e Príncipe)+239
  • Saudi Arabia (‫المملكة العربية السعودية‬‎)+966
  • Senegal (Sénégal)+221
  • Serbia (Србија)+381
  • Seychelles+248
  • Sierra Leone+232
  • Singapore+65
  • Sint Maarten+1
  • Slovakia (Slovensko)+421
  • Slovenia (Slovenija)+386
  • Solomon Islands+677
  • Somalia (Soomaaliya)+252
  • South Africa+27
  • South Korea (대한민국)+82
  • South Sudan (‫جنوب السودان‬‎)+211
  • Spain (España)+34
  • Sri Lanka (ශ්‍රී ලංකාව)+94
  • Sudan (‫السودان‬‎)+249
  • Suriname+597
  • Svalbard and Jan Mayen+47
  • Sweden (Sverige)+46
  • Switzerland (Schweiz)+41
  • Syria (‫سوريا‬‎)+963
  • Taiwan (台灣)+886
  • Tajikistan+992
  • Tanzania+255
  • Thailand (ไทย)+66
  • Timor-Leste+670
  • Togo+228
  • Tokelau+690
  • Tonga+676
  • Trinidad and Tobago+1
  • Tunisia (‫تونس‬‎)+216
  • Turkey (Türkiye)+90
  • Turkmenistan+993
  • Turks and Caicos Islands+1
  • Tuvalu+688
  • U.S. Virgin Islands+1
  • Uganda+256
  • Ukraine (Україна)+380
  • United Arab Emirates (‫الإمارات العربية المتحدة‬‎)+971
  • United Kingdom+44
  • United States+1
  • Uruguay+598
  • Uzbekistan (Oʻzbekiston)+998
  • Vanuatu+678
  • Vatican City (Città del Vaticano)+39
  • Venezuela+58
  • Vietnam (Việt Nam)+84
  • Wallis and Futuna (Wallis-et-Futuna)+681
  • Western Sahara (‫الصحراء الغربية‬‎)+212
  • Yemen (‫اليمن‬‎)+967
  • Zambia+260
  • Zimbabwe+263
  • Åland Islands+358
  • United States+1
  • United Kingdom+44
  • Afghanistan (‫افغانستان‬‎)+93
  • Albania (Shqipëri)+355
  • Algeria (‫الجزائر‬‎)+213
  • American Samoa+1
  • Andorra+376
  • Angola+244
  • Anguilla+1
  • Antigua and Barbuda+1
  • Argentina+54
  • Armenia (Հայաստան)+374
  • Aruba+297
  • Ascension Island+247
  • Australia+61
  • Austria (Österreich)+43
  • Azerbaijan (Azərbaycan)+994
  • Bahamas+1
  • Bahrain (‫البحرين‬‎)+973
  • Bangladesh (বাংলাদেশ)+880
  • Barbados+1
  • Belarus (Беларусь)+375
  • Belgium (België)+32
  • Belize+501
  • Benin (Bénin)+229
  • Bermuda+1
  • Bhutan (འབྲུག)+975
  • Bolivia+591
  • Bosnia and Herzegovina (Босна и Херцеговина)+387
  • Botswana+267
  • Brazil (Brasil)+55
  • British Indian Ocean Territory+246
  • British Virgin Islands+1
  • Brunei+673
  • Bulgaria (България)+359
  • Burkina Faso+226
  • Burundi (Uburundi)+257
  • Cambodia (កម្ពុជា)+855
  • Cameroon (Cameroun)+237
  • Canada+1
  • Cape Verde (Kabu Verdi)+238
  • Caribbean Netherlands+599
  • Cayman Islands+1
  • Central African Republic (République centrafricaine)+236
  • Chad (Tchad)+235
  • Chile+56
  • China (中国)+86
  • Christmas Island+61
  • Cocos (Keeling) Islands+61
  • Colombia+57
  • Comoros (‫جزر القمر‬‎)+269
  • Congo (DRC) (Jamhuri ya Kidemokrasia ya Kongo)+243
  • Congo (Republic) (Congo-Brazzaville)+242
  • Cook Islands+682
  • Costa Rica+506
  • Côte d’Ivoire+225
  • Croatia (Hrvatska)+385
  • Cuba+53
  • Curaçao+599
  • Cyprus (Κύπρος)+357
  • Czech Republic (Česká republika)+420
  • Denmark (Danmark)+45
  • Djibouti+253
  • Dominica+1
  • Dominican Republic (República Dominicana)+1
  • Ecuador+593
  • Egypt (‫مصر‬‎)+20
  • El Salvador+503
  • Equatorial Guinea (Guinea Ecuatorial)+240
  • Eritrea+291
  • Estonia (Eesti)+372
  • Eswatini+268
  • Ethiopia+251
  • Falkland Islands (Islas Malvinas)+500
  • Faroe Islands (Føroyar)+298
  • Fiji+679
  • Finland (Suomi)+358
  • France+33
  • French Guiana (Guyane française)+594
  • French Polynesia (Polynésie française)+689
  • Gabon+241
  • Gambia+220
  • Georgia (საქართველო)+995
  • Germany (Deutschland)+49
  • Ghana (Gaana)+233
  • Gibraltar+350
  • Greece (Ελλάδα)+30
  • Greenland (Kalaallit Nunaat)+299
  • Grenada+1
  • Guadeloupe+590
  • Guam+1
  • Guatemala+502
  • Guernsey+44
  • Guinea (Guinée)+224
  • Guinea-Bissau (Guiné Bissau)+245
  • Guyana+592
  • Haiti+509
  • Honduras+504
  • Hong Kong (香港)+852
  • Hungary (Magyarország)+36
  • Iceland (Ísland)+354
  • India (भारत)+91
  • Indonesia+62
  • Iran (‫ایران‬‎)+98
  • Iraq (‫العراق‬‎)+964
  • Ireland+353
  • Isle of Man+44
  • Israel (‫ישראל‬‎)+972
  • Italy (Italia)+39
  • Jamaica+1
  • Japan (日本)+81
  • Jersey+44
  • Jordan (‫الأردن‬‎)+962
  • Kazakhstan (Казахстан)+7
  • Kenya+254
  • Kiribati+686
  • Kosovo+383
  • Kuwait (‫الكويت‬‎)+965
  • Kyrgyzstan (Кыргызстан)+996
  • Laos (ລາວ)+856
  • Latvia (Latvija)+371
  • Lebanon (‫لبنان‬‎)+961
  • Lesotho+266
  • Liberia+231
  • Libya (‫ليبيا‬‎)+218
  • Liechtenstein+423
  • Lithuania (Lietuva)+370
  • Luxembourg+352
  • Macau (澳門)+853
  • Madagascar (Madagasikara)+261
  • Malawi+265
  • Malaysia+60
  • Maldives+960
  • Mali+223
  • Malta+356
  • Marshall Islands+692
  • Martinique+596
  • Mauritania (‫موريتانيا‬‎)+222
  • Mauritius (Moris)+230
  • Mayotte+262
  • Mexico (México)+52
  • Micronesia+691
  • Moldova (Republica Moldova)+373
  • Monaco+377
  • Mongolia (Монгол)+976
  • Montenegro (Crna Gora)+382
  • Montserrat+1
  • Morocco (‫المغرب‬‎)+212
  • Mozambique (Moçambique)+258
  • Myanmar (Burma) (မြန်မာ)+95
  • Namibia (Namibië)+264
  • Nauru+674
  • Nepal (नेपाल)+977
  • Netherlands (Nederland)+31
  • New Caledonia (Nouvelle-Calédonie)+687
  • New Zealand+64
  • Nicaragua+505
  • Niger (Nijar)+227
  • Nigeria+234
  • Niue+683
  • Norfolk Island+672
  • North Korea (조선 민주주의 인민 공화국)+850
  • North Macedonia (Северна Македонија)+389
  • Northern Mariana Islands+1
  • Norway (Norge)+47
  • Oman (‫عُمان‬‎)+968
  • Pakistan (‫پاکستان‬‎)+92
  • Palau+680
  • Palestine (‫فلسطين‬‎)+970
  • Panama (Panamá)+507
  • Papua New Guinea+675
  • Paraguay+595
  • Peru (Perú)+51
  • Philippines+63
  • Poland (Polska)+48
  • Portugal+351
  • Puerto Rico+1
  • Qatar (‫قطر‬‎)+974
  • Réunion (La Réunion)+262
  • Romania (România)+40
  • Russia (Россия)+7
  • Rwanda+250
  • Saint Barthélemy+590
  • Saint Helena+290
  • Saint Kitts and Nevis+1
  • Saint Lucia+1
  • Saint Martin (Saint-Martin (partie française))+590
  • Saint Pierre and Miquelon (Saint-Pierre-et-Miquelon)+508
  • Saint Vincent and the Grenadines+1
  • Samoa+685
  • San Marino+378
  • São Tomé and Príncipe (São Tomé e Príncipe)+239
  • Saudi Arabia (‫المملكة العربية السعودية‬‎)+966
  • Senegal (Sénégal)+221
  • Serbia (Србија)+381
  • Seychelles+248
  • Sierra Leone+232
  • Singapore+65
  • Sint Maarten+1
  • Slovakia (Slovensko)+421
  • Slovenia (Slovenija)+386
  • Solomon Islands+677
  • Somalia (Soomaaliya)+252
  • South Africa+27
  • South Korea (대한민국)+82
  • South Sudan (‫جنوب السودان‬‎)+211
  • Spain (España)+34
  • Sri Lanka (ශ්‍රී ලංකාව)+94
  • Sudan (‫السودان‬‎)+249
  • Suriname+597
  • Svalbard and Jan Mayen+47
  • Sweden (Sverige)+46
  • Switzerland (Schweiz)+41
  • Syria (‫سوريا‬‎)+963
  • Taiwan (台灣)+886
  • Tajikistan+992
  • Tanzania+255
  • Thailand (ไทย)+66
  • Timor-Leste+670
  • Togo+228
  • Tokelau+690
  • Tonga+676
  • Trinidad and Tobago+1
  • Tunisia (‫تونس‬‎)+216
  • Turkey (Türkiye)+90
  • Turkmenistan+993
  • Turks and Caicos Islands+1
  • Tuvalu+688
  • U.S. Virgin Islands+1
  • Uganda+256
  • Ukraine (Україна)+380
  • United Arab Emirates (‫الإمارات العربية المتحدة‬‎)+971
  • United Kingdom+44
  • United States+1
  • Uruguay+598
  • Uzbekistan (Oʻzbekiston)+998
  • Vanuatu+678
  • Vatican City (Città del Vaticano)+39
  • Venezuela+58
  • Vietnam (Việt Nam)+84
  • Wallis and Futuna (Wallis-et-Futuna)+681
  • Western Sahara (‫الصحراء الغربية‬‎)+212
  • Yemen (‫اليمن‬‎)+967
  • Zambia+260
  • Zimbabwe+263
  • Åland Islands+358
Whatsapp
Whatsapp

+91 7904514634

Teams
Microsoft Teams

@craitrix

Telegram
Telegram

@craitrix