biztrac. BETA
COMPANY REGISTER PROFILE
923301399 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BOGSTADVEIEN 42 NÆRING AS

Org. no. 923301399 Limited company (AS) Oslo Incorporated 2019 Active
Revenue 2025 NOK 3.8m
Operating profit NOK −5.2m
Equity NOK 2.6m
Incorporated 2019
Share capital NOK 184,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5,2 mill kr).

BOGSTADVEIEN 42 NÆRING AS is registered as a limited company in Oslo, Oslo with organisation number 923301399. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 184,000, divided into 183911 shares. The company's stated purpose is: “Eie fast eiendom og delta i selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK −5.2m in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
▲ +2 %
Operating profit
NOK −5.2m
▼ −359 %
Equity
NOK 2.6m
▼ −16 %
Est. value
NOK 4.5m

Financial health · 2025

Liquidity
4.85
Very good
Current assets ÷ current liabilities
Profitability
-29.6%
Not satisfactory
Return on total assets
Solidity
13.3%
Satisfactory
Equity as a share of total capital

Who owns BOGSTADVEIEN 42 NÆRING AS?

BOGSTADVEIEN 42 NÆRING AS
NOK 3.8m rev. · NOK −5.2m profit

BOGSTADVEIEN 42 NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOGSTADVEIEN 42 NÆRING AS

Who owns BOGSTADVEIEN 42 NÆRING AS?

SANDVOLDGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of BOGSTADVEIEN 42 NÆRING AS?

BOGSTADVEIEN 42 NÆRING AS had revenue of NOK 3.8m in 2025.

Where is BOGSTADVEIEN 42 NÆRING AS based?

BOGSTADVEIEN 42 NÆRING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.