> ## Documentation Index
> Fetch the complete documentation index at: https://help.cloudtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 🇳🇴 Norway Number Porting Guide

> A guide for porting your Norwegian numbers to CloudTalk

> [!NOTE]
>
> This guide outlines the supported number types, required documents, hosting rules, and porting timelines for Norwegian numbers.

## Initial Overview

### Supported Number Types

| **Number Type** | **Format Example** |
| - | - |
| Geographic (Local) | e.g., +47 21, +47 23 +47-**2** - *Oslo* +47-**32** - *Buskerud and Jan Mayen* +47-**33** - *Vestfold* +47-**35** - *Telemark* +47-**37** - *Aust-Agder* +47-**38** - *Vest-Agder* +47-**5** - *South-western counties, including Bergen* +47-**6** - *South-eastern counties and Oppland* +47-**7** - *Møre og Romsdal, Trøndelag (Trondheim) and northern Norway* +47-**79** - *Svalbard* |
| National | e.g., 85 xxx xxx |
| Toll-Free | e.g., 800 xxx xx |

> [!NOTE]
>
> ⚠️ Mobile numbers (+47 4xx or +47 9xx) are not portable to VoIP operators.

### Submit Your Request

Request porting directly in the CloudTalk Dashboard: open **Numbers > Port existing number** and follow the guided steps. All supported number types for this country use the same flow, and you can track your request anytime under **Numbers > Porting requests**.

> [!WARNING]
>
> Looking to port numbers from other countries? See **[Global Porting Coverage](https://help.cloudtalk.io/en/articles/5440566-porting-pricing-and-coverage.md)**.

### Letter of Authorization

Where an LOA is required, the correct template for this country **downloads inside the Documents step** of your porting request: download it, sign it, and upload it right there. You no longer need a separate template from this guide.

(Other document requirements listed below.)

### Timelines & Pricing

| **Number Type** | **Estimated Duration** | **Price** |
| - | - | - |
| Local | \~17 business days | **€30.00** per request, **€5.00** per number |
| National | \~17 business days | **€30.00** per request, **€5.00** per number |
| Toll-Free | \~17 business days | **€30.00** per request, **€5.00** per number |

> [!WARNING]
>
> ⚠️ Timelines may vary if submitted details do not match your current provider’s records.

***

## Required Documents for Number Porting

* Signed LOA (completed and signed by an authorized representative; details must match provider records)

* Recent invoice (issued within the last 30 days; must show number(s) and account holder name)

#### Compliance Requirement for Hosting

* Business registration certificate

  * Must be issued or updated within the last 12 months

  * Must show a valid address in Norway

  * Issued by the **[Brønnøysund Register Center](https://www.brreg.no)** (official government registry of legal entities in Norway)

- Norwegian Government-issued ID or Norwegian Passport of someone shown on the business registration. *If the ID holder is not shown, then a Power of Attorney is needed.*

***

## Porting Process Overview

1. **Submit Your Porting Request**\
   Submit your request in the CloudTalk Dashboard under **Numbers > Port existing number**.

2. **Initial Review**\
   Cloudtalk team will verify number portability and confirm the next steps.

3. **Documentation Collection**\
   Complete and sign the LOA (Letter of Authorization), and provide a recent invoice from your current telecom provider.

4. **Submission to Carrier**\
   CloudTalk submits your request to our partner carrier, who then forwards it to your current provider.

5. **Approval or Rejection**

   * If **approved**, Cloudtalk team will confirm the porting date (typically 2–4 business days in advance).

   * If **rejected**, Cloudtalk team will share the reason and guide you on how to correct and resubmit the request.

***

## Common Rejection Reasons

| **Issue** | **Explanation** | **How to Fix** |
| - | - | - |
| **Missing Registration** | Business registration not submitted or expired | Submit updated certificate from Brønnøysund Register Center |
| **Mismatched Info** | Invoice or LOA details do not match provider records | Confirm your data with the provider before submitting the LOA |
| **Inactive Number** | Number has been deactivated or is no longer valid | Ask your provider to reactivate the number |
| **Outdated Invoice** | Invoice is older than 30 days | Submit a recent billing document with matching number details |
| **Number is part of a Range** | This number is part of a block of numbers and can't be ported out individually | Ask your current provider if the number can be split into individual numbers so it can be ported away |

***

## On Porting Day

* The number will be activated in CloudTalk

* Your previous provider will release and deactivate the number

* You’ll begin receiving inbound calls through CloudTalk

* CloudTalk billing begins the same day

***

**Need Help?**

For further assistance, please refer to:

* [CloudTalk Porting Process Overview](https://help.cloudtalk.io/en/articles/2145454-porting-requests-and-process.md)

* [CloudTalk Recommendations for a Smooth Port](https://help.cloudtalk.io/en/articles/6084486-recommendations-for-a-smooth-port.md)

* [Porting Pricing and Coverage](https://help.cloudtalk.io/en/articles/5440566-porting-pricing-and-coverage.md) - all countries where we offer porting

* [Country Specific Porting Guides](https://help.cloudtalk.io/en/articles/5440566-porting-pricing-and-coverage.md) - for our most requested countries

Questions about a request you've already submitted? Open it under **Numbers > Porting requests** and click **Open conversation**. You can also reach our [Porting](mailto:porting@cloudtalk.io) team by email. We're always happy to help!


## Related topics

- [🇦🇺 Australia Number Porting Guide](https://help.cloudtalk.io/en/articles/11069749-australia-number-porting-guide.md)
- [🇦🇹 Austria Number Porting Guide](https://help.cloudtalk.io/en/articles/11458799-austria-number-porting-guide.md)
- [🇮🇱 Israel Number Porting guide](https://help.cloudtalk.io/en/articles/11458866-israel-number-porting-guide.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.