BIZTRAC BETA
Publishing of books

MIMIR FORLAG AS

Org. no. 934197062 Limited company (AS) Nordre Follo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 778,000
Operating profit NOK 184,000
Equity NOK 146,000
Incorporated 2024
Share capital NOK 30,000

MIMIR FORLAG AS is registered as a limited company in Nordre Follo, Akershus with organisation number 934197062. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive audiovisuell produksjon og forlagsvirksomhet, herunder, men ikke begrenset til, utvelgelse, redigering, design, trykking, publisering, markedsføring og distribusjon av bøker, og design, utvikling, programmering, markedsføring og distribusjon av dataspill, mobilspill og alle andre relevante trykte og digitale materialer, samt produkter knyttet til disse.”. The most recent filed accounts, for the 2024 financial year, show NOK 778,000 in revenue and NOK 184,000 in operating profit.

Key figures · 2024

Revenue
NOK 778,000
Operating profit
NOK 184,000
Equity
NOK 146,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns MIMIR FORLAG AS?

ØYVIND HARTLØFF HELLAND
MIMIR FORLAG AS
NOK 778,000 rev. · NOK 184,000 profit

MIMIR FORLAG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIMIR FORLAG AS

Who owns MIMIR FORLAG AS?

ØYVIND HARTLØFF HELLAND is the largest registered owner, with 100.0%.

What is the revenue of MIMIR FORLAG AS?

MIMIR FORLAG AS had revenue of NOK 778,000 in 2024.

Where is MIMIR FORLAG AS based?

MIMIR FORLAG AS has its business address in Langhus.

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.