BIZTRAC BETA
Other cleaning activities

ISAKSEN VEDLIKEHOLD AS

Org. no. 996847470 Limited company (AS) Skien Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 7.3m
Operating profit NOK 1.1m
Equity NOK 3.6m
Incorporated 2011
Share capital NOK 100,000

ISAKSEN VEDLIKEHOLD AS is registered as a limited company in Skien, Telemark with organisation number 996847470. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive med feiing og rengjøring av gater og parkeringsområder, reparasjon og vedlikehold av bygg/eiendom og hva som naturlig hører sammen med dette samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.3m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 7.3m
Operating profit
NOK 1.1m
Equity
NOK 3.6m
Est. value
NOK 6.2m

Financial health · 2024

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

Who owns ISAKSEN VEDLIKEHOLD AS?

CARL EINAR ISAKSEN
ISAKSEN VEDLIKEHOLD AS
NOK 7.3m rev. · NOK 1.1m profit

ISAKSEN VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ISAKSEN VEDLIKEHOLD AS

Who owns ISAKSEN VEDLIKEHOLD AS?

CARL EINAR ISAKSEN is the largest registered owner, with 100.0%.

What is the revenue of ISAKSEN VEDLIKEHOLD AS?

ISAKSEN VEDLIKEHOLD AS had revenue of NOK 7.3m in 2024.

Who is the general manager of ISAKSEN VEDLIKEHOLD AS?

Carl Einar Isaksen is registered as general manager of ISAKSEN VEDLIKEHOLD AS.

Where is ISAKSEN VEDLIKEHOLD AS based?

ISAKSEN VEDLIKEHOLD AS has its business address in Skien.

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.