BIZTRAC BETA
Rental and operating of own or leased real estate

MIRAKAS AS

Org. no. 990024251 Limited company (AS) Flekkefjord Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 250,000
Operating profit NOK 45,000
Equity NOK 363,000
Incorporated 2006
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MIRAKAS AS is registered as a limited company in Flekkefjord, Agder with organisation number 990024251. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investeringer, utvikling og drift av fast eiendom og hva dermed står i forbindelse, herunder også investeringer i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 250,000 in revenue and NOK 45,000 in operating profit.

Key figures · 2024

Revenue
NOK 250,000
Operating profit
NOK 45,000
Equity
NOK 363,000
Est. value
NOK 326,000

Financial health · 2024

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

Who owns MIRAKAS AS?

ANDERSEN HOLDING AS
MIRAKAS AS
NOK 250,000 rev. · NOK 45,000 profit

MIRAKAS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIRAKAS AS

Who owns MIRAKAS AS?

ANDERSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MIRAKAS AS?

MIRAKAS AS had revenue of NOK 250,000 in 2024.

Who is the general manager of MIRAKAS AS?

Per Gunnar Andersen is registered as general manager of MIRAKAS AS.

Where is MIRAKAS AS based?

MIRAKAS AS has its business address in Flekkefjord.

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.