BIZTRAC BETA
Buying and selling of own real estate

SMESTADTOPPEN BOLIG OG UTLEIE AS

Org. no. 923004246 Limited company (AS) Aurskog-Høland Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK −101,000
Equity NOK 136,000
Incorporated 2019
Share capital NOK 2.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−101k kr).

SMESTADTOPPEN BOLIG OG UTLEIE AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 923004246. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 2.5m, divided into 2500 shares. The company's stated purpose is: “Kjøp og salg av eiendom, samt utleie av maskiner og utstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK −101,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK −101,000
Equity
NOK 136,000
Est. value
NOK 9.8m

Financial health · 2024

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

Who owns SMESTADTOPPEN BOLIG OG UTLEIE AS?

TOR UNNEBERG
SMESTADTOPPEN BOLIG OG UTLEIE AS
NOK 8.5m rev. · NOK −101,000 profit

SMESTADTOPPEN BOLIG OG UTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMESTADTOPPEN BOLIG OG UTLEIE AS

Who owns SMESTADTOPPEN BOLIG OG UTLEIE AS?

TOR UNNEBERG is the largest registered owner, with 100.0%.

What is the revenue of SMESTADTOPPEN BOLIG OG UTLEIE AS?

SMESTADTOPPEN BOLIG OG UTLEIE AS had revenue of NOK 8.5m in 2024.

Where is SMESTADTOPPEN BOLIG OG UTLEIE AS based?

SMESTADTOPPEN BOLIG OG UTLEIE AS has its business address in Bjørkelangen.

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.