biztrac. BETA
COMPANY REGISTER PROFILE
927988879 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

HEGBOM FERIEBOLIGER AS

Org. no. 927988879 Limited company (AS) Oslo Incorporated 2021 Active
Revenue 2025 NOK 85,000
Operating profit NOK −103,000
Equity NOK 3.6m
Incorporated 2021
Share capital NOK 4.2m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−103k kr).

HEGBOM FERIEBOLIGER AS is registered as a limited company in Oslo, Oslo with organisation number 927988879. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 4.2m, divided into 4150 shares. The company's stated purpose is: “Utvikling, salg, drift og utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 85,000 in revenue and NOK −103,000 in operating profit.

Key figures · 2025

Revenue
NOK 85,000
▼ −27 %
Operating profit
NOK −103,000
▲ +12 %
Equity
NOK 3.6m
▲ +15 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-2.7%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns HEGBOM FERIEBOLIGER AS?

HEGBOM FERIEBOLIGER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEGBOM FERIEBOLIGER AS

Who owns HEGBOM FERIEBOLIGER AS?

Børre Hegbom is the largest registered owner, with 30.0%.

What is the revenue of HEGBOM FERIEBOLIGER AS?

HEGBOM FERIEBOLIGER AS had revenue of NOK 85,000 in 2025.

Who is the general manager of HEGBOM FERIEBOLIGER AS?

Henning Sigurd Hegbom is registered as general manager of HEGBOM FERIEBOLIGER AS.

Where is HEGBOM FERIEBOLIGER AS based?

HEGBOM FERIEBOLIGER 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.