Article summary
Understand Norway’s +47 country code, eight-digit mobile format, 0047 conversion and a practical QA workflow for WhatsApp number lists.
+47 is the country code for Norway. The prefix 0047 represents the same country code when 00 is used as the international dialing prefix. For data storage and WhatsApp list processing, a consistent canonical form such as country code plus national number is easier to deduplicate and reconcile than a mixture of +47, 0047 and domestic display formats.
Norway’s ordinary fixed and mobile services use eight-digit national numbers. That makes a normalized Norwegian mobile number 10 digits when stored as 47 plus the eight-digit national number, before considering any leading plus sign used for display.
Decode the three forms you are likely to receive
| Observed form | Meaning | Canonical data action |
|---|---|---|
| +47 412 34 567 | International display format | Retain country code 47 and eight national digits; remove spaces for TXT |
| 0047 41234567 | International dialing prefix 00 plus Norway code | Replace the leading 0047 representation with canonical country code 47 |
| 41234567 | Eight-digit national number with Norway known from context | Add 47 only when the source country is reliably Norway |
| 47 41234567 | Data form containing country code and national number | Remove separators and keep 4741234567 |
The examples are illustrative. Do not infer Norway from length alone; other countries can produce the same digit count.
Use Nkom as the numbering authority
Norway’s communications authority, Nkom, states that ITU assigned country code 47 to Norway and that Nkom manages the national numbering plan. Its English numbering overview lists 40–49 and 90–99 among eight-digit mobile-service ranges, alongside other service categories. See Nkom’s numbering resources.
Range assignments can change. Use the current Nkom plan when classifying a large commercial dataset, and avoid assuming that a prefix permanently identifies one carrier because number portability can break that inference.
Separate display formatting from the join key
Store two versions when downstream teams need readable numbers: a canonical digit-only key and a formatted display value. The canonical key supports deduplication, TXT preparation and joining. The display value supports customer-service screens and reports.
Never repeatedly transform the same column in place. Keep the raw source value, normalized key, detected country and validation note. This lets an analyst reverse a faulty rule without returning to the original CRM export.
A Norway-specific normalization routine
- Trim whitespace and remove parentheses, hyphens and non-dialing characters.
- If the string begins with 0047, treat 00 as the international prefix and preserve 47.
- If it begins with +47, remove the plus for a digit-only key.
- If it has exactly eight digits, add 47 only when a trusted country field says Norway.
- Flag all other lengths and conflicting country fields for review.
- Deduplicate on the normalized 47-plus-eight-digit key.
Why mobile-prefix shortcuts need care
Nkom’s broad structure helps distinguish service categories, but prefix ranges are not a substitute for current allocation data. Some number categories have different lengths, and machine-to-machine ranges can differ from ordinary mobile numbers. A simple regular expression should validate the expected project scope, not claim that every syntactically possible number is an active human mobile subscription.
Portability also means the original range does not reliably identify the current network provider. If carrier information is business-critical, obtain it from an appropriate current source rather than deriving it from an old prefix spreadsheet.
Prepare a Norwegian WhatsApp checking sample
Keep the authorized CRM extract locally, including source ID and permission status. Create a TXT file with one normalized number per line. Include a pilot mix of +47, 0047 and domestic source forms after they have been converted to the same canonical representation.
Choose the WS/WA task according to the desired output. Registration checking returns a registration-status result; activity and profile-related services return different field sets. Do not use a broad task when the decision requires only registration.
Reconcile the Excel result without losing Norwegian source context
AIPUSH returns Excel for the selected WhatsApp number-checking task. Import the workbook into a staging table and ensure phone-number cells are treated as text. Reapply the documented canonical rule, then join to the internal 47-prefixed key.
Report input unique count, output unique count, successful joins and exception rows. Keep mapped WhatsApp numbers in a separate column when the chosen task returns them. A difference between submitted and mapped values should be reviewed, not silently overwritten.
Five errors that create false duplicates or failed joins
- Keeping both +47 and 0047 as if they were different country codes.
- Adding 47 to a number that already contains the country code.
- Assuming every eight-digit value in a mixed-country file is Norwegian.
- Letting Excel convert the number to scientific notation.
- Using spaces or punctuation inconsistently between input and output keys.
Final QA card for +47 data
A Norway list is ready for processing when every included row has a traceable source, a reliable country assignment, eight national digits in the intended mobile scope, one canonical 47-prefixed key and a documented permission state. Syntax alone does not prove that a number exists, is registered on WhatsApp or can be contacted.
Use the numbering plan to make the input coherent, the WhatsApp task to return the selected technical fields, and the company’s own governance rules to decide what happens next. Keeping those three layers separate prevents a formatting correction from being mistaken for audience qualification.
