BIZTRAC BETA
Buying and selling of own real estate

MUNCOR AS

Org. no. 925348031 Limited company (AS) Kristiansand Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK 7.3m
Incorporated 2020
Share capital NOK 30,000

Signals

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

MUNCOR AS is registered as a limited company in Kristiansand, Agder with organisation number 925348031. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i annen forretningsvirksomhet, eiendom og verdipapirer og annet som naturlig faller sammen med dette. Herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 7.3m
Est. value
NOK 21.5m

Financial health · 2024

Liquidity
151.91
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns MUNCOR AS?

PETER SCOTT MUNK
MUNCOR AS
NOK 0 rev. · NOK −18,000 profit

MUNCOR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MUNCOR AS own?

MUNCOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MUNCOR AS

Who owns MUNCOR AS?

PETER SCOTT MUNK is the largest registered owner, with 100.0%.

What is the revenue of MUNCOR AS?

MUNCOR AS had revenue of NOK 0 in 2024.

Where is MUNCOR AS based?

MUNCOR AS has its business address in Søgne.

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.