BIZTRAC BETA
Development of building projects

BOGERUDVEIEN 15 BOLIG AS

Org. no. 926292331 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 86.8m
Operating profit NOK 2.9m
Equity NOK 243,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

BOGERUDVEIEN 15 BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 926292331. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom, kjøp og salg av verdipapirer, samt annen virksomhet som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 86.8m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 86.8m
Operating profit
NOK 2.9m
Equity
NOK 243,000
Est. value
NOK 5.1m

Financial health · 2024

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.6%
Not satisfactory
Equity as a share of total capital

Who owns BOGERUDVEIEN 15 BOLIG AS?

GJELSTEN BOLIG AS
BOGERUDVEIEN 15 BOLIG AS
NOK 86.8m rev. · NOK 2.9m profit

BOGERUDVEIEN 15 BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOGERUDVEIEN 15 BOLIG AS

Who owns BOGERUDVEIEN 15 BOLIG AS?

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

What is the revenue of BOGERUDVEIEN 15 BOLIG AS?

BOGERUDVEIEN 15 BOLIG AS had revenue of NOK 86.8m in 2024.

Where is BOGERUDVEIEN 15 BOLIG AS based?

BOGERUDVEIEN 15 BOLIG 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.