BIZTRAC BETA
Arts creation activities in literature

MAGISK KUNNSKAP AS

Org. no. 927209632 Limited company (AS) Ringsaker Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK −205,000
Equity NOK 624,000
Incorporated 2021
Share capital NOK 432,000

Signals

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

MAGISK KUNNSKAP AS is registered as a limited company in Ringsaker, Innlandet with organisation number 927209632. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2021. Registered share capital is NOK 432,000, divided into 1440 shares. The company's stated purpose is: “Forfatter, utvikler og distribuerer digitale læremidler samt annen for formålet hensiktsmessig virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK −205,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK −205,000
Equity
NOK 624,000
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns MAGISK KUNNSKAP AS?

TONE EVENSEN
MAGISK KUNNSKAP AS
NOK 3.7m rev. · NOK −205,000 profit

MAGISK KUNNSKAP AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about MAGISK KUNNSKAP AS

Who owns MAGISK KUNNSKAP AS?

TONE EVENSEN is the largest registered owner, with 75.2%.

What is the revenue of MAGISK KUNNSKAP AS?

MAGISK KUNNSKAP AS had revenue of NOK 3.7m in 2024.

Who is the general manager of MAGISK KUNNSKAP AS?

Tone Evensen is registered as general manager of MAGISK KUNNSKAP AS.

Where is MAGISK KUNNSKAP AS based?

MAGISK KUNNSKAP AS has its business address in Brumunddal.

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.