BIZTRAC BETA
Rental and operating of own or leased real estate

HYBELBYGG AS

Org. no. 952286870 Limited company (AS) Hammerfest Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 269,000
Operating profit NOK −133,000
Equity NOK 7.9m
Incorporated 1989
Share capital NOK 6.7m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−133k kr).

HYBELBYGG AS is registered as a limited company in Hammerfest, Finnmark with organisation number 952286870. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1989. Registered share capital is NOK 6.7m, divided into 13400 shares. The company's stated purpose is: “Eie og leie ut fast eiendom, samt det som naturlig hører inn under dette. Selskapet skal også kunne drive med eiendomsutvikling for videresalg.”. The most recent filed accounts, for the 2024 financial year, show NOK 269,000 in revenue and NOK −133,000 in operating profit.

Key figures · 2024

Revenue
NOK 269,000
Operating profit
NOK −133,000
Equity
NOK 7.9m
Est. value
NOK 7.2m

Financial health · 2024

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

Who owns HYBELBYGG AS?

TORMOD BARTHOLDSEN
HYBELBYGG AS
NOK 269,000 rev. · NOK −133,000 profit

HYBELBYGG AS has 15 registered shareholders:

All shareholders and roles →

Which companies does HYBELBYGG AS own?

HYBELBYGG AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about HYBELBYGG AS

Who owns HYBELBYGG AS?

TORMOD BARTHOLDSEN is the largest registered owner, with 59.7%.

What is the revenue of HYBELBYGG AS?

HYBELBYGG AS had revenue of NOK 269,000 in 2024.

Where is HYBELBYGG AS based?

HYBELBYGG AS has its business address in Hammerfest.

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.