BIZTRAC BETA
Rental and operating of own or leased real estate

BOGSTADVEIEN 24 AS

Org. no. 813194252 Limited company (AS) Oslo Incorporated 1966 Active
Ownership graph ↗
Revenue 2024 NOK 285,000
Operating profit NOK 127,000
Equity NOK 5.4m
Incorporated 1966
Share capital NOK 100,000

Signals

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

BOGSTADVEIEN 24 AS is registered as a limited company in Oslo, Oslo with organisation number 813194252. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1966. Registered share capital is NOK 100,000. The company's stated purpose is: “Investere i 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 285,000 in revenue and NOK 127,000 in operating profit.

Key figures · 2024

Revenue
NOK 285,000
Operating profit
NOK 127,000
Equity
NOK 5.4m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns BOGSTADVEIEN 24 AS?

TANDBERG EIENDOM AS
BOGSTADVEIEN 24 AS
NOK 285,000 rev. · NOK 127,000 profit

BOGSTADVEIEN 24 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BOGSTADVEIEN 24 AS er morselskap for 33 datterselskaper:

Frequently asked questions about BOGSTADVEIEN 24 AS

Who owns BOGSTADVEIEN 24 AS?

TANDBERG EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BOGSTADVEIEN 24 AS?

BOGSTADVEIEN 24 AS had revenue of NOK 285,000 in 2024.

Where is BOGSTADVEIEN 24 AS based?

BOGSTADVEIEN 24 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.