BIZTRAC BETA
Wholesale of information and communication equipment

SNUSEXPRESS I NORGE AS

Org. no. 890280862 Limited company (AS) Indre Østfold Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 25.7m
Operating profit NOK 920,000
Equity NOK 2.4m
Incorporated 2006
Share capital NOK 500,000

SNUSEXPRESS I NORGE AS is registered as a limited company in Indre Østfold, Østfold with organisation number 890280862. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2006. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Handel med kontorsutstyr og datautstyr, handel med og utleie av eiendom, handel med verdipapirer, kjøp og salg, import og salg av tobakk, nikotin og nikotinfrie produkter til forhandlere og privatpersoner i butikk og online, samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.7m in revenue and NOK 920,000 in operating profit.

Key figures · 2025

Revenue
NOK 25.7m
Operating profit
NOK 920,000
Equity
NOK 2.4m
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.8%
Satisfactory
Equity as a share of total capital

Who owns SNUSEXPRESS I NORGE AS?

SALT LABS AB
SNUSEXPRESS I NORGE AS
NOK 25.7m rev. · NOK 920,000 profit

SNUSEXPRESS I NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNUSEXPRESS I NORGE AS

Who owns SNUSEXPRESS I NORGE AS?

SALT LABS AB is the largest registered owner, with 100.0%.

What is the revenue of SNUSEXPRESS I NORGE AS?

SNUSEXPRESS I NORGE AS had revenue of NOK 25.7m in 2025.

Where is SNUSEXPRESS I NORGE AS based?

SNUSEXPRESS I NORGE AS has its business address in Hærland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.