biztrac. BETA
COMPANY REGISTER PROFILE
979121393 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of adventure companies

MIKKELGAMMEN AS

Org. no. 979121393 Limited company (AS) Hammerfest Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 698,000
Operating profit NOK −124,000
Equity NOK 266,000
Incorporated 1997
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−124k kr).

MIKKELGAMMEN AS is registered as a limited company in Hammerfest, Finnmark with organisation number 979121393. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 20 shares. The company's stated purpose is: “Drive samisk opplevelsestilbud.”. The most recent filed accounts, for the 2024 financial year, show NOK 698,000 in revenue and NOK −124,000 in operating profit.

Key figures · 2024

Revenue
NOK 698,000
▼ −21 %
Operating profit
NOK −124,000
▼ −500 %
Equity
NOK 266,000
▼ −33 %
Est. value
NOK 780,000

Financial health · 2024

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
-15.3%
Not satisfactory
Return on total assets
Solidity
30.7%
Good
Equity as a share of total capital

Who owns MIKKELGAMMEN AS?

MIKKELGAMMEN AS
NOK 698,000 rev. · NOK −124,000 profit

MIKKELGAMMEN AS has 2 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about MIKKELGAMMEN AS

Who owns MIKKELGAMMEN AS?

Mikkel Nils Andersen Sara is the largest registered owner, with 50.0%.

What is the revenue of MIKKELGAMMEN AS?

MIKKELGAMMEN AS had revenue of NOK 698,000 in 2024.

Where is MIKKELGAMMEN AS based?

MIKKELGAMMEN AS has its business address in Hammerfest.

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.