BIZTRAC BETA
Construction of residential and non-residential buildings

HOLTEFJELL LAFT AS

Org. no. 997627628 Limited company (AS) Modum Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 356,000
Operating profit NOK −210,000
Equity NOK 1.3m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−210k kr).

HOLTEFJELL LAFT AS is registered as a limited company in Modum, Buskerud with organisation number 997627628. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Snekker/-tømrervirksomhet, alt innen stav og laft nybygg og restaurering.”. The most recent filed accounts, for the 2025 financial year, show NOK 356,000 in revenue and NOK −210,000 in operating profit.

Key figures · 2025

Revenue
NOK 356,000
Operating profit
NOK −210,000
Equity
NOK 1.3m
Est. value
NOK 690,000

Financial health · 2025

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

Who owns HOLTEFJELL LAFT AS?

OLE KRISTIAN GRØNLUND
HOLTEFJELL LAFT AS
NOK 356,000 rev. · NOK −210,000 profit

HOLTEFJELL LAFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOLTEFJELL LAFT AS

Who owns HOLTEFJELL LAFT AS?

OLE KRISTIAN GRØNLUND is the largest registered owner, with 100.0%.

What is the revenue of HOLTEFJELL LAFT AS?

HOLTEFJELL LAFT AS had revenue of NOK 356,000 in 2025.

Who is the general manager of HOLTEFJELL LAFT AS?

Arnfinn Jellum is registered as general manager of HOLTEFJELL LAFT AS.

Where is HOLTEFJELL LAFT AS based?

HOLTEFJELL LAFT AS has its business address in Skotselv.

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.