BIZTRAC BETA
COMPANY REGISTER PROFILE
834957752 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SMØRSTEIN AS

Org. no. 834957752 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 480,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

SMØRSTEIN AS is registered as a limited company in Drammen, Buskerud with organisation number 834957752. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i aksjer og verdipapirer og alt som hører naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 480,000
Est. value
NOK 294,000

Financial health · 2025

Liquidity
29.62
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
65.6%
Very good
Equity as a share of total capital

Who owns SMØRSTEIN AS?

SMØRSTEIN AS
NOK 0 rev. · NOK −2,000 profit

SMØRSTEIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SMØRSTEIN AS own?

SMØRSTEIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SMØRSTEIN AS

Who owns SMØRSTEIN AS?

MADS WESTLIE GUNDERSEN is the largest registered owner, with 100.0%.

What is the revenue of SMØRSTEIN AS?

SMØRSTEIN AS had revenue of NOK 0 in 2025.

Who is the general manager of SMØRSTEIN AS?

Mads Westlie Gundersen is registered as general manager of SMØRSTEIN AS.

Where is SMØRSTEIN AS based?

SMØRSTEIN AS has its business address in Drammen.

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

Report a problem

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