biztrac. BETA
COMPANY REGISTER PROFILE
918339396 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Support services to forestry

KNUTSEN UTEMILJØ AS

Org. no. 918339396 Limited company (AS) Eidsvoll Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 13.5m
Operating profit NOK 657,000
Equity NOK 5.8m
Incorporated 2016
Employees 18
Share capital NOK 50,000

KNUTSEN UTEMILJØ AS is registered as a limited company in Eidsvoll, Akershus with organisation number 918339396. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2016 and has 18 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Skogdrift, snøbrøyting, graving, anleggsgartnerarbeid og annen virksomhet som naturlig faller sammen med dette eller som styret finner interessant.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.5m in revenue and NOK 657,000 in operating profit.

Former names: KNUTSEN SKOGSTJENESTER AS

Key figures · 2025

Revenue
NOK 13.5m
▲ +5 %
Operating profit
NOK 657,000
▼ −34 %
Equity
NOK 5.8m
▲ +5 %
Est. value
NOK 4.6m

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
5.1%
Weak
Return on total assets
Solidity
46.0%
Very good
Equity as a share of total capital

Who owns KNUTSEN UTEMILJØ AS?

KNUTSEN UTEMILJØ AS
NOK 13.5m rev. · NOK 657,000 profit

KNUTSEN UTEMILJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KNUTSEN UTEMILJØ AS

Who owns KNUTSEN UTEMILJØ AS?

Audun Knutsen is the largest registered owner, with 100.0%.

What is the revenue of KNUTSEN UTEMILJØ AS?

KNUTSEN UTEMILJØ AS had revenue of NOK 13.5m in 2025.

Where is KNUTSEN UTEMILJØ AS based?

KNUTSEN UTEMILJØ AS has its business address in Eidsvoll.

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.