BIZTRAC BETA
Computer consultancy and computer facilities management activities

JUNGLEMAP AS

Org. no. 984590423 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 50.1m
Operating profit NOK 7.4m
Equity NOK 4.9m
Incorporated 2002
Employees 15
Share capital NOK 161,000

JUNGLEMAP AS is registered as a limited company in Oslo, Oslo with organisation number 984590423. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2002 and has 15 registered employees. Registered share capital is NOK 161,000, divided into 1613 shares. The company's stated purpose is: “Rådgivning og utvikling av programvare for opplæring og organisasjonsutvikling, samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 50.1m in revenue and NOK 7.4m in operating profit.

Key figures · 2024

Revenue
NOK 50.1m
Operating profit
NOK 7.4m
Equity
NOK 4.9m
Est. value
NOK 29.8m

Financial health · 2024

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.4%
Weak
Equity as a share of total capital

Who owns JUNGLEMAP AS?

METACOMPLIANCE NORDICS AS
JUNGLEMAP AS
NOK 50.1m rev. · NOK 7.4m profit

JUNGLEMAP AS has 1 registered shareholder:

All shareholders and roles →

Group structure

JUNGLEMAP AS er morselskap for 14 datterselskaper:

Frequently asked questions about JUNGLEMAP AS

Who owns JUNGLEMAP AS?

METACOMPLIANCE NORDICS AS is the largest registered owner, with 100.0%.

What is the revenue of JUNGLEMAP AS?

JUNGLEMAP AS had revenue of NOK 50.1m in 2024.

Who is the general manager of JUNGLEMAP AS?

Goran Govorcinovic is registered as general manager of JUNGLEMAP AS.

Where is JUNGLEMAP AS based?

JUNGLEMAP 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.