BIZTRAC BETA
Uoppgitt

EGENBOLIG.NO AS

Org. no. 918331646 Limited company (AS) Tønsberg Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −12,000
Equity NOK −98,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−98k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

EGENBOLIG.NO AS is registered as a limited company in Tønsberg, Vestfold with organisation number 918331646. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift og forvaltning av Egenbolig.no AS sitt eget konsept ved utleie og drift av boligmasse, hvor det inngås leiekontrakter med rett til kjøp og det som naturlig hører inn under dette, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK −98,000

Financial health · 2024

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1126.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EGENBOLIG.NO AS?

JENS MORTEN THORSEN
EGENBOLIG.NO AS
NOK 0 rev. · NOK −12,000 profit

EGENBOLIG.NO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EGENBOLIG.NO AS

Who owns EGENBOLIG.NO AS?

JENS MORTEN THORSEN is the largest registered owner, with 50.0%.

What is the revenue of EGENBOLIG.NO AS?

EGENBOLIG.NO AS had revenue of NOK 0 in 2024.

Where is EGENBOLIG.NO AS based?

EGENBOLIG.NO AS has its business address in Tønsberg.

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.