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

HOLMEN BYGG AS

Org. no. 935255597 Limited company (AS) Etne Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 72,000
Equity NOK 59,000
Incorporated 2025
Share capital NOK 30,000

HOLMEN BYGG AS is registered as a limited company in Etne, Vestland with organisation number 935255597. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Snekkervirksomhet med oppføring og vedlikehold av bygninger og anlegg, salg av materialer og anna som naturlig hører under snekkervirksomhet. Investeringsvirksomhet, herunder å eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 72,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 72,000
Equity
NOK 59,000
Est. value
NOK 212,000

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
9.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HOLMEN BYGG AS?

HOLMEN BYGG AS
NOK 1.0m rev. · NOK 72,000 profit

HOLMEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOLMEN BYGG AS

Who owns HOLMEN BYGG AS?

Jens Inge Haugland Holmen is the largest registered owner, with 100.0%.

What is the revenue of HOLMEN BYGG AS?

HOLMEN BYGG AS had revenue of NOK 1.0m in 2025.

Where is HOLMEN BYGG AS based?

HOLMEN BYGG AS has its business address in Etne.

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.