BIZTRAC BETA
Rental and operating of own or leased real estate

KLEMSDAL INVEST AS

Org. no. 911552841 Limited company (AS) Fredrikstad Incorporated 1949 Active
Ownership graph ↗
Revenue 2025 NOK 11.6m
Operating profit NOK 4.6m
Equity NOK 10.7m
Incorporated 1949
Share capital NOK 200,000

KLEMSDAL INVEST AS is registered as a limited company in Fredrikstad, Østfold with organisation number 911552841. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1949. Registered share capital is NOK 200,000, divided into 50 shares. The company's stated purpose is: “Å eie, forvalte, kjøpe og selge fast eiendom, aksjer og andre verdipapirer, faktisk og formell deltagelse i andre selskaper av lignende art, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.6m in revenue and NOK 4.6m in operating profit.

Key figures · 2025

Revenue
NOK 11.6m
Operating profit
NOK 4.6m
Equity
NOK 10.7m
Est. value
NOK 15.2m

Financial health · 2025

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.8%
Satisfactory
Equity as a share of total capital

Who owns KLEMSDAL INVEST AS?

KLEMSDAL HOLDING AS
KLEMSDAL INVEST AS
NOK 11.6m rev. · NOK 4.6m profit

KLEMSDAL INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLEMSDAL INVEST AS

Who owns KLEMSDAL INVEST AS?

KLEMSDAL HOLDING AS is the largest registered owner, with 84.0%.

What is the revenue of KLEMSDAL INVEST AS?

KLEMSDAL INVEST AS had revenue of NOK 11.6m in 2025.

Who is the general manager of KLEMSDAL INVEST AS?

Arne Trond Klemsdal is registered as general manager of KLEMSDAL INVEST AS.

Where is KLEMSDAL INVEST AS based?

KLEMSDAL INVEST AS has its business address in Fredrikstad.

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.