BIZTRAC BETA
Support services to forestry

ENDRESTØL SKOGSDRIFT AS

Org. no. 919897732 Limited company (AS) Hol Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK −109,000
Equity NOK 741,000
Incorporated 2017
Share capital NOK 100,000

Signals

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

ENDRESTØL SKOGSDRIFT AS is registered as a limited company in Hol, Buskerud with organisation number 919897732. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Entreprenør innen skogbruk. Samt andre produkter og tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK −109,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK −109,000
Equity
NOK 741,000
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns ENDRESTØL SKOGSDRIFT AS?

EIVIND ENDRESTØL
ENDRESTØL SKOGSDRIFT AS
NOK 4.0m rev. · NOK −109,000 profit

ENDRESTØL SKOGSDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENDRESTØL SKOGSDRIFT AS

Who owns ENDRESTØL SKOGSDRIFT AS?

EIVIND ENDRESTØL is the largest registered owner, with 100.0%.

What is the revenue of ENDRESTØL SKOGSDRIFT AS?

ENDRESTØL SKOGSDRIFT AS had revenue of NOK 4.0m in 2025.

Who is the general manager of ENDRESTØL SKOGSDRIFT AS?

Eivind Endrestøl is registered as general manager of ENDRESTØL SKOGSDRIFT AS.

Where is ENDRESTØL SKOGSDRIFT AS based?

ENDRESTØL SKOGSDRIFT AS has its business address in Geilo.

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.