BIZTRAC BETA
Wholesale of other machinery and equipment

HYBEKO AS

Org. no. 991729380 Limited company (AS) Skien Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 343.6m
Operating profit NOK 12.9m
Equity NOK 74.9m
Incorporated 2007
Employees 74
Share capital NOK 3.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HYBEKO AS is registered as a limited company in Skien, Telemark with organisation number 991729380. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2007 and has 74 registered employees. Registered share capital is NOK 3.0m, divided into 501 shares. The company's stated purpose is: “Salg av løfte- og transportutstyr til industrien samt dertil hørende virksomhet. Selskapet kan også drive handel i finansielle instrumenter.”. The most recent filed accounts, for the 2024 financial year, show NOK 343.6m in revenue and NOK 12.9m in operating profit.

Key figures · 2024

Revenue
NOK 343.6m
Operating profit
NOK 12.9m
Equity
NOK 74.9m
Est. value
NOK 77.8m

Financial health · 2024

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.7%
Good
Equity as a share of total capital

Who owns HYBEKO AS?

HYKO INVEST AS
HYBEKO AS
NOK 343.6m rev. · NOK 12.9m profit

HYBEKO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HYBEKO AS

Who owns HYBEKO AS?

HYKO INVEST AS is the largest registered owner, with 74.5%.

What is the revenue of HYBEKO AS?

HYBEKO AS had revenue of NOK 343.6m in 2024.

Who is the general manager of HYBEKO AS?

Espen Johannessen is registered as general manager of HYBEKO AS.

Where is HYBEKO AS based?

HYBEKO AS has its business address in Skien.

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.