BIZTRAC BETA
Landscape service activities

KLEVELAND'S UTEMILJØ AS

Org. no. 989376357 Limited company (AS) Trondheim Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 19.5m
Operating profit NOK 1.5m
Equity NOK 3.9m
Incorporated 2006
Employees 9
Share capital NOK 400,000

KLEVELAND'S UTEMILJØ AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989376357. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2006 and has 9 registered employees. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Gartner-, anleggstjenester og alt som hermed står i forbindelse, og å delta i andre selskaper ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.5m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 19.5m
Operating profit
NOK 1.5m
Equity
NOK 3.9m
Est. value
NOK 8.3m

Financial health · 2025

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

Who owns KLEVELAND'S UTEMILJØ AS?

DAGFINN KLEVELAND
KLEVELAND'S UTEMILJØ AS
NOK 19.5m rev. · NOK 1.5m profit

KLEVELAND'S UTEMILJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLEVELAND'S UTEMILJØ AS

Who owns KLEVELAND'S UTEMILJØ AS?

DAGFINN KLEVELAND is the largest registered owner, with 100.0%.

What is the revenue of KLEVELAND'S UTEMILJØ AS?

KLEVELAND'S UTEMILJØ AS had revenue of NOK 19.5m in 2025.

Who is the general manager of KLEVELAND'S UTEMILJØ AS?

Dagfinn Kleveland is registered as general manager of KLEVELAND'S UTEMILJØ AS.

Where is KLEVELAND'S UTEMILJØ AS based?

KLEVELAND'S UTEMILJØ AS has its business address in Trondheim.

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.