biztrac. BETA
COMPANY REGISTER PROFILE
920236286 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

JOHAN KJELLMARK HOLDING AS

Org. no. 920236286 Limited company (AS) Røros Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −50,000
Equity NOK 29.5m
Incorporated 2017
Share capital NOK 210,000

Signals

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

JOHAN KJELLMARK HOLDING AS is registered as a limited company in Røros, Trøndelag with organisation number 920236286. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 210,000, divided into 210 shares. The company's stated purpose is: “Investeringer i andre selskap og fast eiendom samt annen virksomhet som naturlig hører inn under dette.”.

Former names: KJELLMARKGRUPPEN AS

Key figures · 2025

Operating profit
NOK −50,000
▲ +65 %
Equity
NOK 29.5m
▼ −0 %
Est. value
NOK 24.0m

Financial health · 2025

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
96.5%
Very good
Equity as a share of total capital

Who owns JOHAN KJELLMARK HOLDING AS?

JOHAN KJELLMARK HOLDING AS has 13 registered shareholders:

All shareholders and roles →

Which companies does JOHAN KJELLMARK HOLDING AS own?

JOHAN KJELLMARK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

JOHAN KJELLMARK HOLDING AS er morselskap for 5 datterselskaper:

Frequently asked questions about JOHAN KJELLMARK HOLDING AS

Who owns JOHAN KJELLMARK HOLDING AS?

Arnstein Kjellmark is the largest registered owner, with 23.8%.

Where is JOHAN KJELLMARK HOLDING AS based?

JOHAN KJELLMARK HOLDING AS has its business address in Røros.

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.