BIZTRAC BETA
Rental and operating of own or leased real estate

BREILIVEIEN 41 AS

Org. no. 991743391 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 4.0m
Equity NOK 16.9m
Incorporated 2007
Share capital NOK 875,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BREILIVEIEN 41 AS is registered as a limited company in Oslo, Oslo with organisation number 991743391. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 875,000, divided into 875 shares. The company's stated purpose is: “Investering i fast eiendom, herunder utleie, drift, kjøp og salg, samt investering i aksjer og andre verdipapirer, herunder aktiv deltagelse i andre selskaper. I tillegg kommer annen nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 4.0m in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK 4.0m
Equity
NOK 16.9m
Est. value
NOK 17.5m

Financial health · 2025

Liquidity
1.67
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.0%
Good
Equity as a share of total capital

Who owns BREILIVEIEN 41 AS?

H-2 EIENDOM AS
BREILIVEIEN 41 AS
NOK 5.6m rev. · NOK 4.0m profit

BREILIVEIEN 41 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BREILIVEIEN 41 AS

Who owns BREILIVEIEN 41 AS?

H-2 EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BREILIVEIEN 41 AS?

BREILIVEIEN 41 AS had revenue of NOK 5.6m in 2025.

Where is BREILIVEIEN 41 AS based?

BREILIVEIEN 41 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.