BIZTRAC BETA
Buying and selling of own real estate

JUMAR AS

Org. no. 922044503 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK −534,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−534k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

JUMAR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922044503. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i Ruta Entreprenør AS.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK −534,000

Financial health · 2024

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-15.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JUMAR AS?

GUNNESMÆL INVEST AS
JUMAR AS
NOK 0 rev. · NOK −2,000 profit

JUMAR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JUMAR AS own?

JUMAR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JUMAR AS

Who owns JUMAR AS?

GUNNESMÆL INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of JUMAR AS?

JUMAR AS had revenue of NOK 0 in 2024.

Who is the general manager of JUMAR AS?

Erlend Gunnesmæl is registered as general manager of JUMAR AS.

Where is JUMAR AS based?

JUMAR 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.