BIZTRAC BETA
Rental and operating of own or leased real estate

MAGIC PERSONAL AS

Org. no. 915603564 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 12.5m
Operating profit NOK −367,000
Equity NOK 5.4m
Incorporated 2015
Employees 15
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−367k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MAGIC PERSONAL AS is registered as a limited company in Bergen, Vestland with organisation number 915603564. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Drive næringsvirksomhet, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.5m in revenue and NOK −367,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.5m
Operating profit
NOK −367,000
Equity
NOK 5.4m
Est. value
NOK 22.5m

Financial health · 2024

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

Who owns MAGIC PERSONAL AS?

MAGIC NORWAY AS
MAGIC PERSONAL AS
NOK 12.5m rev. · NOK −367,000 profit

MAGIC PERSONAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAGIC PERSONAL AS

Who owns MAGIC PERSONAL AS?

MAGIC NORWAY AS is the largest registered owner, with 100.0%.

What is the revenue of MAGIC PERSONAL AS?

MAGIC PERSONAL AS had revenue of NOK 12.5m in 2024.

Where is MAGIC PERSONAL AS based?

MAGIC PERSONAL AS has its business address in Bergen.

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.