biztrac. BETA
COMPANY REGISTER PROFILE
951365084 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

HOLM AS

Org. no. 951365084 Limited company (AS) Flekkefjord Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 70.0m
Operating profit NOK 5.4m
Equity NOK 10.0m
Incorporated 1989
Employees 22
Share capital NOK 120,000

HOLM AS is registered as a limited company in Flekkefjord, Agder with organisation number 951365084. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1989 and has 22 registered employees. Registered share capital is NOK 120,000, divided into 60 shares. The company's stated purpose is: “Entreprenørvirksomhet og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 70.0m in revenue and NOK 5.4m in operating profit.

Key figures · 2025

Revenue
NOK 70.0m
▼ −12 %
Operating profit
NOK 5.4m
▼ −20 %
Equity
NOK 10.0m
▲ +5 %
Est. value
NOK 22.9m

Financial health · 2025

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
20.1%
Very good
Return on total assets
Solidity
36.0%
Good
Equity as a share of total capital

Who owns HOLM AS?

HOLM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does HOLM AS own?

HOLM AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

HOLM AS er morselskap for 1 datterselskap:

Frequently asked questions about HOLM AS

Who owns HOLM AS?

HOLM EIENDOM AS is the largest registered owner, with 80.0%.

What is the revenue of HOLM AS?

HOLM AS had revenue of NOK 70.0m in 2025.

Who is the general manager of HOLM AS?

Cato Treland is registered as general manager of HOLM AS.

Where is HOLM AS based?

HOLM AS has its business address in Flekkefjord.

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.