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

JEMAR HOLDING AS

Org. no. 814859592 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −210,000
Equity NOK 7.3m
Incorporated 2014
Share capital NOK 30,000

Signals

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

JEMAR HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 814859592. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapslove og utenlandske selskaper, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”.

Former names: JCP HOLDING AS

Key figures · 2025

Operating profit
NOK −210,000
▲ +23 %
Equity
NOK 7.3m
▼ −1 %
Est. value
NOK 5.7m

Financial health · 2025

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

Who owns JEMAR HOLDING AS?

JEMAR HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JEMAR HOLDING AS own?

JEMAR HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JEMAR HOLDING AS

Who owns JEMAR HOLDING AS?

Jens Christian Petersen is the largest registered owner, with 50.0%.

Who is the general manager of JEMAR HOLDING AS?

Marianne Bjørnson Hofstad is registered as general manager of JEMAR HOLDING AS.

Where is JEMAR HOLDING AS based?

JEMAR HOLDING AS has its business address in Oslo.

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.