biztrac. BETA
COMPANY REGISTER PROFILE
925874469 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Industrial product and fashion design activities

MAGPIE AS

Org. no. 925874469 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK 263,000
Incorporated 2020
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−24k kr).
  • Nylig endring 2026-08-10 Adresseendring registrert 2026-08-10.

MAGPIE AS is registered as a limited company in Oslo, Oslo with organisation number 925874469. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Investering og deltakelse i andre selskaper og det som naturlig hører inn under dette. Kjøp og salg av aksjer og eiendom.”.

Key figures · 2025

Operating profit
NOK −24,000
▼ −1 %
Equity
NOK 263,000
▼ −29 %
Est. value
NOK 427,000

Financial health · 2025

Liquidity
124.53
Very good
Current assets ÷ current liabilities
Profitability
-7.4%
Not satisfactory
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns MAGPIE AS?

MAGPIE AS
· NOK −24,000 profit

MAGPIE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MAGPIE AS own?

MAGPIE AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

MAGPIE AS er morselskap for 1 datterselskap:

Frequently asked questions about MAGPIE AS

Who owns MAGPIE AS?

Jo Hass Korneliussen is the largest registered owner, with 100.0%.

Who is the general manager of MAGPIE AS?

Jo Hass Korneliussen is registered as general manager of MAGPIE AS.

Where is MAGPIE AS based?

MAGPIE AS has its business address in Oslo.

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.