Sweden proxies
The Nordic market is built so that one platform serves Sweden, Norway, Denmark and Finland, with the country and the currency chosen by the visitor’s address. On top of that the price comparison layer matters here: a shop page shows the price, but what moves it is happening a floor above, on the aggregator.
What we have in Sweden
Prices are the same as in every other country we cover.
What Swedish addresses get used for
Retail price monitoring
Elgiganten, NetOnNet, Webhallen, Ellos, Åhléns: storefronts are separate from the Norwegian and Danish ones even where the platform is shared.
Price comparison
Prisjakt and PriceRunner set the reference shops reprice against, and their listings diverge from the storefronts.
Classifieds and second-hand
Blocket covers goods, cars and part of the property market here.
Local search and SEO
google.se: Swedish results are their own set, with their own ad blocks.
What looks different from outside Sweden
These serve a Swedish visitor something other than what a foreign one sees, because of broadcast rights and local catalogues. We sell addresses rather than a way past detection.
Which type to take for a Swedish job
Home connection addresses, billed per gigabyte, rotating by default. A sticky session holds one address for up to fifty minutes.
Retail, classifieds, search results, ad checks
Addresses in Swedish datacenters, traffic unmetered.
Volume collection where the target ignores address class
Cities people ask for here
Cities are set with the _city_ suffix. The three largest carry almost the whole pool, and the north is requested rarely.
The setups people take here most often
- 01Residential, country levelThe default: retail and classifieds expect a home address.
- 02A fifty minute sticky sessionWhen a job has to run start to finish on one address.
- 03Datacenter, StockholmVolume collection where the target is neutral.
- 04Sweden apart from its neighboursA separate pass per Nordic country, because the platform is shared and the data is not.
Connection strings for Sweden
The country code is SE, upper case. The city goes after it with _city_, hyphens instead of spaces, in the order country, city, session, lifetime.
Swedish static addresses take no suffixes: the host is the IP from your dashboard, port 50100, SOCKS5 on 50101.
Swedish exits, four ways
curl -x login_c_SE:[email protected]:10000 https://api.ipify.org
# held for fifty minutes, for a job that must not change address
curl -x login_c_SE_s_42_ttl_50m:[email protected]:10000 https://api.ipify.org
# Gothenburg explicitly, when you are comparing regions
curl -x login_c_SE_city_Gothenburg_s_43_ttl_15m:[email protected]:10000 https://api.ipify.org
# a Swedish static address: no suffixes
curl -x login:password@YOUR-SE-IP:50100 https://api.ipify.orgOne platform, four Nordic countries
The defining feature of the region, and the one that costs the most when it goes unnoticed.
Nordic chains usually run one shop across four markets. The domain may be shared or separate, but the content is substituted by country: its own currency, its own range, its own delivery windows, its own promotions. Sweden counts in kronor, Finland in euros, Norway and Denmark in their own kronor.
Hence a mistake that looks harmless: collect one shop and label the export "Nordics". What is in it is one country of four, and the numbers in different currencies mix together the first time anyone tries to compare them.
The correct shape of the work: a separate pass per country from that country’s address, currency as a column in the data, and no conversion on the fly. Convert in the report if you like, but store what you were shown.
One pair of requests settles it: the same product page from a Swedish and a Finnish exit. If the currency or the price differs, you have four markets rather than one.
Where the price actually gets set
The second feature, and it is about what to monitor.
In Sweden the comparison layer, Prisjakt and PriceRunner, works as a market rather than a directory: shops watch their position in the list and move the price to stand higher in it. The price on the storefront is the outcome; the cause sits a floor above.
The practical consequence: collecting storefronts alone shows you effects without letting you anticipate movement. Anyone who also collects the aggregator sees a repricing before it reaches every storefront.
The second consequence is technical: aggregator listings and shop pages diverge in time. When you find a difference, do not file it as a collection error straight away. More often it is update lag, and the size of that lag is a useful metric in itself.
Join the two on the seller’s product identifier rather than the name: aggregators normalise titles their own way, and string matching is unreliable here.
What actually blocks you on Swedish targets
Sweden is stricter than the European average about address class.
Retail chains, Blocket and the price aggregators expect a home address: a 403 from datacenter arrives more often and sooner than in neighbouring countries.
Publishers and government sites serve datacenter addresses normally.
Search results are reachable but rate limited per address: more addresses rather than a different type.
On pace specifically: Swedish platforms are noticeably more sensitive to an even machine rhythm than to volume. Jitter in your intervals helps more here than extra addresses.
Which exits you get here, and how stable they are
The Swedish pool in practical terms.
The pool is mid-sized and high quality: a country with deep fibre penetration, fast home lines and some of the best response times in our coverage from Europe.
The distribution is Stockholm-weighted, but Gothenburg and Malmö resolve reliably. The north is requested rarely and the pool there is thin.
Sticky sessions hold an address for up to fifty minutes: when a job has to run on one address from start to finish, that is the tool here.
Default rotation changes the address on every request, which is exactly what collecting listings wants.
Choosing the type for a Swedish target
A short order, because there are two types.
- Start with a Swedish datacenter address: $1.15 per address per month. On news and reference sites that is enough.
- A 403 on the first request means hosting ranges are filtered. On retail and classifieds that happens more often here than across the region.
- Then country-level residential. If the job has to stay on one address, add a sticky session with a lifetime.
- A 429 after many requests is a per-address rate limit: more addresses, not a different type.
- Ask for a city only when comparing regions. Otherwise country level is more reliable.
What Swedish sites check beyond the address
A Swedish address opens the first gate; language and number parsing decide the rest.
Send sv-SE. English versions are common here and handed over readily, so without an explicit header you will happily collect the wrong catalogue.
The currency is the krona, written 1 299,00 kr: a space between thousands, a comma for decimals, and the currency after the number in lower case. That thousands separator is usually non-breaking.
The time zone is CET and shifts in summer. Configure the profile to it rather than to UTC.
Consent banners are mandatory and cover the content: a scraper that does not handle them captures an empty page under a successful status code.
What a month of Swedish work costs
Three scenarios at our prices, so you have something to check a quote against.
- Price monitoring across Swedish retail, 30,000 listings a day with images blocked, roughly 120 KB per page. That is about 3.6 GB a day, around 108 GB a month: $108 on residential.
- Adding a price aggregator on top costs little: its listings are more compact than product pages, and this is single-digit gigabytes on the invoice.
- Four Nordic countries as separate passes are four such budgets. The per-gigabyte price is the same everywhere, so what you are budgeting is volume rather than rate.
The legal part, stated plainly
Sweden is in the European Union, so GDPR applies here with everything that follows for collecting personal data. A Swedish address neither puts you under it nor takes you out: what matters is whose data you collect, not where the traffic exits.
This is general information rather than legal advice. Our terms require lawful use and we act on abuse reports. Where the answer carries commercial risk, ask a lawyer.
Verifying a Swedish exit
Under a minute. The second command matters more than the first: it shows that a shared platform is giving you the Swedish market.
Three checks
# 1. is the exit Swedish, and where
curl -s -x login_c_SE:[email protected]:10000 https://ipinfo.io/json
# 2. the same page, two Nordic markets
curl -s -H "Accept-Language: sv-SE" -x login_c_SE:[email protected]:10000 https://your-target.com/product | grep -oE "[0-9 ]+,[0-9]{2} kr" | head -3
curl -s -H "Accept-Language: fi-FI" -x login_c_FI:[email protected]:10000 https://your-target.com/product | grep -oE "[0-9 ]+,[0-9]{2} ?€" | head -3
# 3. does the fifty minute session hold
for i in 1 2 3; do
curl -s -x login_c_SE_s_42_ttl_50m:[email protected]:10000 https://api.ipify.org; echo
doneQuestions people ask before buying Swedish addresses
Can the Nordics be collected in one pass?
No. The platform is shared, but country, currency and range are substituted from the visitor’s address, so this is four separate passes and four sets of data.
Why collect the price aggregators?
Because shops reprice against their position there. Storefronts show you the outcome; the aggregator shows the movement earlier.
What if a job has to run from one address?
Use a sticky session with a lifetime: it holds one residential address for up to fifty minutes.
Why does datacenter fail more often here?
Swedish retail and Blocket are stricter than the regional average about hosting ranges. On news and reference sites datacenter works normally.
Why am I getting the English version?
English versions are handed over readily here. Send sv-SE explicitly or you will collect the wrong catalogue.
Do Swedish addresses cost more?
No. Prices are the same everywhere: residential from $1.00 per GB, datacenter from $1.15 per address per month.