Article summary
Svalbard contacts use Norway’s +47 numbering plan. Learn how to classify number types, separate project sources, and interpret WhatsApp activity fields as dated cohorts rather than regional behaviour.
Svalbard contact records often combine an address, a duty station and a phone number under one country label. The telephone itself still belongs to Norway’s +47 numbering plan. A useful Svalbard WhatsApp activity workflow therefore separates three facts: why the contact is connected to Svalbard, what kind of +47 number was submitted, and when the activity job was run.
Practical principle: +47 identifies the numbering framework, Svalbard identifies project provenance, and the returned activity fields describe a dated observation. None of those fields can substitute for the other two.
Why a Svalbard number looks Norwegian
The Norwegian Communications Authority states that the ITU assigned country code 47 to Norway and that Nkom manages the national plan beneath it. Its English numbering resource lists eight-digit ranges for fixed and mobile services, with 40–49 and 90–99 used for mobile numbers, as well as separate ranges for special and machine-to-machine services.
Svalbard does not have a distinct personal-phone country code. A +47 value can be associated with a resident, researcher, supplier or traveller, but the prefix alone cannot place that person in Longyearbyen or any other settlement.
Staff turnover changes the meaning of an old contact list
Statistics Norway’s Svalbard population series reports settlements and migration at half-year intervals. The series covers Longyearbyen and Ny-Ålesund and also reports other settlements. That recurring movement is a warning against treating a multi-year directory as a stable audience.
Retain the collection period, the screening date and the end date of the relevant relationship. An activity value from a 2026 contractor directory should not be blended with a 2023 visitor enquiry and labelled as a general Svalbard usage rate.
Route +47 values by number type before screening
| Observed shape | Initial classification | Workflow decision |
|---|---|---|
| Eight digits after +47, beginning 4 or 9 | Mobile-shaped | Retain when project provenance is documented |
| Eight digits in another ordinary range | Potential fixed or other service | Review against the current Nkom plan |
| Twelve digits after +47 beginning 58 | Machine-to-machine / IoT-shaped | Exclude from a personal contact workflow |
| Eight local digits without +47 | Incomplete international representation | Add the country code only when the source schema supports it |
Range allocation is a format and service clue, not a dependable current-carrier label. Number portability makes an old allocation lookup unsuitable as a substitute for live carrier data.
Build cohorts around comparable business windows
A research station directory, a tour operator’s booking list and an engineering supplier file represent different relationships. Screen them as separate cohorts. The internal batch sheet can hold the source system, collection dates, relationship type and last-confirmed date, while the uploaded text file contains phone numbers only.
| Cohort | Useful time anchor | Records to keep out |
|---|---|---|
| On-duty personnel | Current roster or contract term | Former staff from an archived directory |
| Travel-service customers | Booking and itinerary window | Old one-off enquiries with no continuing relationship |
| Operational suppliers | Active purchase or maintenance cycle | Publicly found numbers with no supplier record |
What the four WS Activity fields contribute
Choose WS Activity on the AppShai WhatsApp Number Checker and upload a TXT file with one number per line. The resulting Excel file contains the phone number, activity time, activity days and WhatsApp mapped phone number. Keep those returned fields intact and add your own batch metadata in separate columns.
WhatsApp’s own explanation of last seen and online says that visibility can be affected by privacy settings, prior contact, blocking and temporary connection conditions. A blank or unavailable value therefore must not be translated into “never uses WhatsApp.”
Create a freshness ladder before opening the export
Define recent, intermediate, older and unknown bands according to the actual service cycle. A same-week travel disruption and a quarterly equipment contract do not need the same threshold. Write the thresholds before seeing the distribution so that the analyst does not move the boundary to produce a more attractive chart.
| Band | Evidence rule | Operational interpretation |
|---|---|---|
| Recent | Falls inside the pre-declared short window | Eligible for time-sensitive service messages when permission exists |
| Intermediate | Outside the short window but inside an active relationship | Check the latest booking, roster or order |
| Older | Substantially outside the relevant cycle | Lower priority; do not launch an unsolicited reactivation blast |
| Unknown | No interpretable activity value | Preserve as unknown instead of converting it to zero |
Treat a mapped number as a review signal
When the mapped WhatsApp number differs from the submitted number, retain both values and the execution date. Return to the authorised customer or personnel record before making any identity decision. Two records that map to the same value should not be merged automatically, and the mapped value should not silently replace the number supplied by the individual.
A master contact record requires stronger evidence, such as a fresh confirmation or a documented service event. Activity screening can reveal an inconsistency; it does not resolve ownership by itself.
Three attractive but invalid Svalbard metrics
- “Share of Svalbard residents active on WhatsApp.” A +47 list cannot establish residency or a population denominator.
- “Zero days means inactive.” Unavailable visibility and a confirmed zero are not the same observation.
- “The winter list improved over summer.” The comparison fails when the source populations and relationships changed.
A reproducible statement is narrower: within a named source list, version and execution date, a stated number of authorized contacts fell inside a pre-set activity window. That statement carries enough context for another reviewer to repeat the calculation.
Field-team control list
- Store Svalbard as project provenance, not as a separate telephone country code.
- Use the current Nkom plan to distinguish ordinary mobile, fixed and machine ranges.
- Keep research, travel and supplier cohorts separate.
- Upload one number per TXT line and preserve all four Excel service fields.
- Predefine recency bands and keep missing observations as unknown.
- Do not overwrite a source number with a mapped value.
- Act only within a valid organisational or customer relationship.
Small lists do not justify casual assumptions. With source, number class and time kept apart, a Svalbard activity job can support rosters, bookings and service operations without pretending to describe an entire region.
