BIZTRAC BETA
Rental and operating of own or leased real estate

BEOL EIENDOM AS

Org. no. 925984604 Limited company (AS) Hurdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 392,000
Operating profit NOK 229,000
Equity NOK −253,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−253k kr).

BEOL EIENDOM AS is registered as a limited company in Hurdal, Akershus with organisation number 925984604. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Erverv, utvikling, drift og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 392,000 in revenue and NOK 229,000 in operating profit.

Key figures · 2025

Revenue
NOK 392,000
Operating profit
NOK 229,000
Equity
NOK −253,000
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
-31.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7.8%
Weak
Equity as a share of total capital

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

Who owns BEOL EIENDOM AS?

TOM BERTINUSSEN
BEOL EIENDOM AS
NOK 392,000 rev. · NOK 229,000 profit

BEOL EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BEOL EIENDOM AS

Who owns BEOL EIENDOM AS?

TOM BERTINUSSEN is the largest registered owner, with 34.0%.

What is the revenue of BEOL EIENDOM AS?

BEOL EIENDOM AS had revenue of NOK 392,000 in 2025.

Who is the general manager of BEOL EIENDOM AS?

Tom Bertinussen is registered as general manager of BEOL EIENDOM AS.

Where is BEOL EIENDOM AS based?

BEOL EIENDOM AS has its business address in Hurdal.

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.