BIZTRAC BETA
Buying and selling of own real estate

BOGAVEIEN EIENDOM AS

Org. no. 925520578 Limited company (AS) Steinkjer Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −51,000
Equity NOK −963,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−963k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−51k kr).

BOGAVEIEN EIENDOM AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 925520578. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, drift, salg av fast eiendom og det som står i forbindelse med dette, herunder i andre selskaper med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −51,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −51,000
Equity
NOK −963,000

Financial health · 2025

Liquidity
9.58
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-8.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BOGAVEIEN EIENDOM AS?

FERGELAND EIENDOM AS
BOGAVEIEN EIENDOM AS
NOK 0 rev. · NOK −51,000 profit

BOGAVEIEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOGAVEIEN EIENDOM AS

Who owns BOGAVEIEN EIENDOM AS?

FERGELAND EIENDOM AS is the largest registered owner, with 66.7%.

What is the revenue of BOGAVEIEN EIENDOM AS?

BOGAVEIEN EIENDOM AS had revenue of NOK 0 in 2025.

Where is BOGAVEIEN EIENDOM AS based?

BOGAVEIEN EIENDOM AS has its business address in Steinkjer.

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.