biztrac. BETA
COMPANY REGISTER PROFILE
984144725 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Site preparation

HYLLAND AS

Org. no. 984144725 Limited company (AS) Bergen Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 175.9m
Operating profit NOK 15.9m
Equity NOK 27.2m
Incorporated 2002
Employees 46
Share capital NOK 400,000

HYLLAND AS is registered as a limited company in Bergen, Vestland with organisation number 984144725. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2002 and has 46 registered employees. Registered share capital is NOK 400,000, divided into 200 shares. The company's stated purpose is: “Anleggsvirksomhet, transport, inn- og utleie av maskiner samt det som naturlig står i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 175.9m in revenue and NOK 15.9m in operating profit.

Key figures · 2025

Revenue
NOK 175.9m
▲ +13 %
Operating profit
NOK 15.9m
▲ +70 %
Equity
NOK 27.2m
▲ +6 %
Est. value
NOK 60.5m

Financial health · 2025

Liquidity
1.50
Good
Current assets ÷ current liabilities
Profitability
21.0%
Very good
Return on total assets
Solidity
30.1%
Good
Equity as a share of total capital

Who owns HYLLAND AS?

HYLLAND AS
NOK 175.9m rev. · NOK 15.9m profit

HYLLAND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HYLLAND AS own?

HYLLAND AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HYLLAND AS

Who owns HYLLAND AS?

BLOMSTRING AS is the largest registered owner, with 100.0%.

What is the revenue of HYLLAND AS?

HYLLAND AS had revenue of NOK 175.9m in 2025.

Who is the general manager of HYLLAND AS?

Kjell Trengereid is registered as general manager of HYLLAND AS.

Where is HYLLAND AS based?

HYLLAND AS has its business address in Godvik.

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.