Send SMS to Sweden
from $0.0220/msg

Mobile Operators and Interconnect Coverage

Telia Company (36% market share): Sweden's largest operator and the country's former national telecommunications incumbent. Telia owns and operates the backbone of Swedish fixed and mobile networks. All A2P SMS sent via smsroute route through Telia's core HLR (home location register) with direct interconnect, ensuring sub-200-millisecond latency to Telia subscribers. Telia enforces PTS compliance rules on inbound A2P traffic.

Vodafone Sweden (31% market share): The second-largest operator. Vodafone Sweden runs both 4G LTE and 5G networks and carries almost one-third of Swedish mobile traffic. smsroute maintains a direct interconnect to Vodafone's A2P SMS gateway, with SLA uptime of 99.9%. Vodafone's network is geographically distributed; latency to Vodafone subscribers averages 180 ms.

Telenor Sweden (26% market share): The third-largest operator and a pan-Nordic carrier. Telenor Sweden operates under the same compliance framework as the other operators and delivers SMS with identical latency and success metrics. Telenor subscribers make up over one-quarter of Sweden's mobile base and are reached via smsroute's standard interconnect.

Tele2 Sweden (7% market share): A smaller operator but a material portion of the Swedish market. Tele2 carries MVNO traffic (mobile virtual network operator customers) and has a significant IoT SMS segment. smsroute's network includes Tele2 routing, ensuring no subscriber is excluded. Tele2 enforces the same quiet hours and consent rules as the larger operators.

All four operators interconnect with smsroute via dedicated peering agreements. There are no separate per-operator fees or discounts; your $0.0220 per SMS rate applies uniformly across all four carriers. Delivery success of 99.2% is measured as an aggregate across all four operators and is independently logged.

Pricing: smsroute vs. Competitors

smsroute's $0.0220 per SMS rate includes all features: API access, REST and SDK support, quiet-hour enforcement, PTS compliance checklists, Reservasjonsregisteret pre-flight validation, and 99.2% delivery success. There are no setup fees, no monthly minimums, and no per-operator surcharges. All competitors listed above charge significantly more per SMS. Twilio, a market leader, costs 56% more. For a 10-million-message annual volume, smsroute saves $1.24 million compared to Twilio.

Payment is cryptocurrency-only: Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. Minimum top-up is $5. No SEPA transfers, no card payments, no PayPal. This keeps operational overhead low and rates competitive. Your balance never expires and can be carried forward indefinitely between campaigns.

Latency and Delivery Performance

smsroute operates edge nodes in Stockholm and across the Nordic region, ensuring fast SMS delivery to Swedish recipients. Median latency (p50) is 185 milliseconds. The 95th-percentile latency (p95) is 340 milliseconds. This means that 95% of SMS to Sweden are delivered within 340 ms of submission — well within consumer expectations for transactional messages and competitive with international carriers.

Overall delivery success is 99.2%, measured as the percentage of SMS that reach the recipient's device without bouncing or being silently dropped. This metric is calculated across all four major Swedish operators (Telia, Vodafone, Telenor, Tele2) and is updated hourly. Uptime across our core infrastructure is 99.9%, meaning the smsroute API is available for sending SMS 99.9% of the time; planned maintenance windows are announced 7 days in advance.

Transactional messages (2FA codes, password resets, payment notifications) are prioritized and typically deliver within 50–100 ms. Marketing SMS respect quiet hours and may be queued if sent outside 09:00–20:00 CET; they will be delivered at the start of the next valid window (usually within minutes).

We do not offer SLA credits or refunds for delivery failures, but we monitor each message end-to-end and provide detailed delivery reports in the dashboard. If a message fails, you will see the reason: invalid number format, number not in Swedish mobile range, recipient on Reservasjonsregisteret, operator rejection (rare), or network timeout (very rare). Use these reports to diagnose and remediate campaign issues.

Consent Rules, Regulator, and Reservasjonsregisteret

The Swedish telecoms regulator is PTS (Post- och Telestyrelsens), officially the Swedish Post and Telecom Authority. PTS enforces Swedish ePrivacy Law and GDPR Articles 21 and 82, which cover unsolicited direct marketing and recipient rights to opt out. PTS publishes enforcement guidance and maintains a public register of complaints and actions against non-compliant senders.

Consent Model: All marketing SMS require explicit opt-in. This means the recipient must actively tick a box, sign a form, or confirm an SMS opt-in request. Consent must be:

• Clear and affirmative (no pre-ticked boxes, no silent defaults).
• Documented and timestamped in your CRM or consent database.
• Separate from other consents (you cannot bundle SMS consent with marketing email or newsletter consent).
• Freely given (not a condition of purchase or service, unless SMS is core to the service delivery itself).

Reservasjonsregisteret: This national registry allows Swedish consumers to register their mobile numbers and request no SMS from marketers. The registry is managed by PTS and is accessible to A2P SMS providers via a published API. Before sending a campaign, import your recipient list and cross-reference it against Reservasjonsregisteret. Any number that appears in the registry must be excluded. We provide a pre-flight API endpoint (`POST /validate/se/dnc-check`) that flags registered numbers in your list within seconds.

Soft Opt-In Exception: Sweden does not recognize a soft opt-in exception. Even if a customer has an existing relationship with your business, you must obtain explicit consent to send them SMS. This is stricter than some other GDPR jurisdictions and is a common compliance failure point.

Transactional Messages: Two-factor authentication (2FA), password resets, payment confirmations, and delivery notifications are not considered marketing and do not require prior consent. However, the SMS must be genuinely transactional; marketing language or promotional upsells in a transactional message invalidate the exemption. Keep transactional and marketing SMS separate.

Quiet Hours: Swedish law restricts marketing SMS to 09:00–20:00 CET, Monday through Friday. No SMS should be sent outside these windows or on weekends. Transactional SMS can be sent 24/7. This is enforced by PTS guidance and is part of consumer protection regulations.

Frequently Asked Questions

Related

const SMSRoute = require('smsroute-node');

const client = new SMSRoute.Client({
  apiKey: 'YOUR_API_KEY'
});

client.send({
  to: '+46712345678',
  from: 'MyBrand',
  text: 'Hello Sweden! Your verification code is 123456.',
  scheduledTime: '2025-03-15T10:30:00+01:00'
}).then(response => {
  console.log('Status:', response.status);
  console.log('Message ID:', response.messageId);
  console.log('Delivery Timestamp:', response.deliveryTimestamp);
}).catch(err => {
  console.error('Error:', err);
});

import os, requests

resp = requests.post(
    "https://api.smsroute.cc/v1/messages",
    headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
    json={
        "to": "+465551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    },
    timeout=10,
)
resp.raise_for_status()
print(resp.json())

curl -X POST https://api.smsroute.cc/send \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "to": "+46712345678",
    "from": "MyBrand",
    "text": "Hello Sweden! Your verification code is 123456.",
    "scheduled_time": "2025-03-15T10:30:00+01:00"
  }'

package main

import (
    "bytes"
    "encoding/json"
    "fmt"
    "io"
    "net/http"
    "os"
)

func main() {
    payload, _ := json.Marshal(map[string]string{
        "to":   "+465551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

    req, _ := http.NewRequest("POST",
        "https://api.smsroute.cc/v1/messages",
        bytes.NewBuffer(payload))
    req.Header.Set("Authorization", "Bearer "+os.Getenv("SMSROUTE_API_KEY"))
    req.Header.Set("Content-Type", "application/json")

    resp, err := http.DefaultClient.Do(req)
    if err != nil { panic(err) }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

<?php
$apiKey = getenv('SMSROUTE_API_KEY');

$payload = json_encode([
    'to'   => '+465551234567',
    'from' => 'smsroute',
    'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);

$ch = curl_init('https://api.smsroute.cc/v1/messages');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . $apiKey,
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => $payload,
]);

echo curl_exec($ch);
curl_close($ch);