BIZTRAC BETA
Development of building projects

EINEÅSEN BOLIG 1 AS

Org. no. 918704825 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 300,000
Operating profit NOK −520,000
Equity NOK 646,000
Incorporated 2016
Share capital NOK 185,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−520k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EINEÅSEN BOLIG 1 AS is registered as a limited company in Oslo, Oslo with organisation number 918704825. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 185,000, divided into 5200 shares. The company's stated purpose is: “Å eie og drifte fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 300,000 in revenue and NOK −520,000 in operating profit.

Key figures · 2024

Revenue
NOK 300,000
Operating profit
NOK −520,000
Equity
NOK 646,000
Est. value
NOK 892,000

Financial health · 2024

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

Who owns EINEÅSEN BOLIG 1 AS?

BOLIG RYKKINN AS
EINEÅSEN BOLIG 1 AS
NOK 300,000 rev. · NOK −520,000 profit

EINEÅSEN BOLIG 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EINEÅSEN BOLIG 1 AS

Who owns EINEÅSEN BOLIG 1 AS?

BOLIG RYKKINN AS is the largest registered owner, with 100.0%.

What is the revenue of EINEÅSEN BOLIG 1 AS?

EINEÅSEN BOLIG 1 AS had revenue of NOK 300,000 in 2024.

Where is EINEÅSEN BOLIG 1 AS based?

EINEÅSEN BOLIG 1 AS has its business address in Oslo.

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.