BIZTRAC BETA
Other non-specialised retail sale

BOLIGSTYRET.NO AS

Org. no. 914183723 Limited company (AS) Frogn Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 27,000
Operating profit NOK −46,000
Equity NOK 187,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

BOLIGSTYRET.NO AS is registered as a limited company in Frogn, Akershus with organisation number 914183723. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Informasjon om regler og rutiner knyttet til faste eiendommers rettsforhold gjennom elektroniske media, samt alt som står forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 27,000 in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK 27,000
Operating profit
NOK −46,000
Equity
NOK 187,000
Est. value
NOK 98,000

Financial health · 2024

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

Who owns BOLIGSTYRET.NO AS?

DAG KRISTEN STADHEIM
BOLIGSTYRET.NO AS
NOK 27,000 rev. · NOK −46,000 profit

BOLIGSTYRET.NO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOLIGSTYRET.NO AS

Who owns BOLIGSTYRET.NO AS?

DAG KRISTEN STADHEIM is the largest registered owner, with 50.0%.

What is the revenue of BOLIGSTYRET.NO AS?

BOLIGSTYRET.NO AS had revenue of NOK 27,000 in 2024.

Who is the general manager of BOLIGSTYRET.NO AS?

Trond Harald Sønju is registered as general manager of BOLIGSTYRET.NO AS.

Where is BOLIGSTYRET.NO AS based?

BOLIGSTYRET.NO AS has its business address in Drøbak.

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.