BIZTRAC BETA
Rental and operating of own or leased real estate

BOGSTADVEIEN 46 B AS

Org. no. 992728817 Limited company (AS) Bærum Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 1.1m
Equity NOK 7.1m
Incorporated 2007
Share capital NOK 134,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 46 B AS is registered as a limited company in Bærum, Akershus with organisation number 992728817. 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 134,000, divided into 2693 shares. The company's stated purpose is: “Å delta i andre selskaper. Selskapet vil tilby kurs og konsulenttjenester samt drive handel. Selskapet vil også kunne drive kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 1.1m
Equity
NOK 7.1m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns BOGSTADVEIEN 46 B AS?

REKSTEN INVEST AS
BOGSTADVEIEN 46 B AS
NOK 1.7m rev. · NOK 1.1m profit

BOGSTADVEIEN 46 B AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOGSTADVEIEN 46 B AS

Who owns BOGSTADVEIEN 46 B AS?

REKSTEN INVEST AS is the largest registered owner, with 77.9%.

What is the revenue of BOGSTADVEIEN 46 B AS?

BOGSTADVEIEN 46 B AS had revenue of NOK 1.7m in 2024.

Where is BOGSTADVEIEN 46 B AS based?

BOGSTADVEIEN 46 B AS has its business address in Sandvika.

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.