BIZTRAC BETA
Uoppgitt

MUNKEREKKA AS

Org. no. 924446951 Limited company (AS) Færder Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6,000
Operating profit NOK −39,000
Equity NOK 503,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

MUNKEREKKA AS is registered as a limited company in Færder, Vestfold with organisation number 924446951. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i andre selskaper, rådgivning, kjøp og salg, samt virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 6,000
Operating profit
NOK −39,000
Equity
NOK 503,000
Est. value
NOK 592,000

Financial health · 2025

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.4%
Good
Equity as a share of total capital

Who owns MUNKEREKKA AS?

KIM BJØRNUNG RYGEL
MUNKEREKKA AS
NOK 6,000 rev. · NOK −39,000 profit

MUNKEREKKA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MUNKEREKKA AS own?

MUNKEREKKA AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about MUNKEREKKA AS

Who owns MUNKEREKKA AS?

KIM BJØRNUNG RYGEL is the largest registered owner, with 50.0%.

What is the revenue of MUNKEREKKA AS?

MUNKEREKKA AS had revenue of NOK 6,000 in 2025.

Who is the general manager of MUNKEREKKA AS?

Kim Bjørnung Rygel is registered as general manager of MUNKEREKKA AS.

Where is MUNKEREKKA AS based?

MUNKEREKKA AS has its business address in Nøtterøy.

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.