Skip to main content

​
Norway Marketing Act Sender Rules (Markedsføringsloven, Nkom)

Norway (NO) is an enabled Orbit destination for voice and SMS, dialing prefix 47. Norwegian marketing traffic sits under the Markedsføringsloven (the Marketing Control Act, act no. 2 of 9 January 2009) together with the e-handelsloven (the e-commerce act), which carry the country’s opt-in rule for electronic direct marketing to individuals. Telecom-side oversight sits with Nkom (the Norwegian Communications Authority); marketing-practice enforcement with the Forbrukertilsynet (the Norwegian Consumer Authority). Norway applies the GDPR and the ePrivacy consent rule through the EEA Agreement, with the national reservasjonsregisteret (reservation register) as the do-not-contact list for covered telephone marketing. This page expands the NO row of the country-requirements matrix so you can assemble the posture before your first Norwegian send. Norway is a tenant-owned burden. Orbit keeps the country-rules reference and the send-time surfaces; the legal posture for your Norwegian recipients is yours.
This page is documentation, not legal advice. The Marketing Control Act’s direct-marketing provisions are enforced against the sender, and the reservation register’s coverage has its own statutory scope. Have counsel review your consent and scrub practice for Norwegian recipients; Orbit supplies the surfaces.

​
Accepted sender types and registration level

Norway operates no statutory alphanumeric sender-ID registry. Norwegian operators accept alphanumeric senders, and the live NO country-rules row reads registration: recommended: registration is a deliverability posture the market argues for, not a statutory filing. Confirm how Norwegian carriers handle your sender before a branded campaign, and file it through Sender-ID Registration where stable branding matters.

​
Opt-in and opt-out posture

Electronic direct marketing to Norwegian individuals requires prior consent; the e-commerce act carries the ePrivacy side of that rule for electronic communications. Record consent before dispatch, and honor revocations on every channel. For voice campaigns, the reservasjonsregisteret is the national scrub layer: registered numbers on the reservation register must not receive covered marketing calls, so scrub it before a Norwegian voice campaign alongside your own suppression ledger.

​
Quiet hours

Norway sets no statutory marketing quiet-hours window for SMS; the recipient’s consent and your own sending policy carry the clock. Orbit’s tenant quiet-hours channel toggles default OFF, per Quiet Hours FAQ; for Norwegian campaigns, opt in a recipient-local window over Europe/Oslo and apply an evening cutoff consistent with your consent basis. The toggle is tenant-owned and fails open until you set it, matching the platform posture that every compliance control except the US federal voice window is yours to configure.

​
Number purchase

Norway is not a member of the platform’s regulated phone_number_purchase set (DE, GB, FR, BR, MX, IN, JP, FI, NL, SE), so a Norwegian number order does not wait on an approved compliance profile. The marketing posture above still applies to the traffic you originate from the number: the purchase gate and the sending posture are separate obligations, and the lighter purchase path does not soften the opt-in rule.

​
Worked configuration before your first Norwegian send

1

Record consent with an sms scope

Capture prior consent for each Norwegian recipient in Consent Management before the first send; store the source and timestamp so the record is producible.
2

Add the Norwegian stop vocabulary

Confirm STOP is active and add STOPP as a Norwegian alias in the opt-out rules editor so Norwegian-language replies suppress immediately.
3

Scrub the reservation register for voice

Before any Norwegian voice campaign, run the DNC Scrub against the reservasjonsregisteret and keep the suppression ledger current for every channel.
4

Set the quiet-hours window

Opt in the tenant quiet-hours toggle for the SMS and voice channels and set a Europe/Oslo evening window per Quiet Hours FAQ.
5

Read the live row and send

Re-read GET /api/v1/compliance/country-rules?country=NO for the current registration and sender_types values, then send. A revocation received on any channel lands in the suppression ledger and blocks the next send to that recipient.