BIZTRAC BETA
Other publishing activities, except software publishing

MÅKEN FORLAG AS

Org. no. 931362453 Limited company (AS) Lørenskog Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 623,000
Operating profit NOK 111,000
Equity NOK 138,000
Incorporated 2023
Share capital NOK 30,000

MÅKEN FORLAG AS is registered as a limited company in Lørenskog, Akershus with organisation number 931362453. The business is classified under other publishing activities, except software publishing (NACE 58.190). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen forlagsvirksomhet og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 623,000 in revenue and NOK 111,000 in operating profit.

Key figures · 2024

Revenue
NOK 623,000
Operating profit
NOK 111,000
Equity
NOK 138,000
Est. value
NOK 727,000

Financial health · 2024

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

Who owns MÅKEN FORLAG AS?

SONJA HELENE DALSETH
MÅKEN FORLAG AS
NOK 623,000 rev. · NOK 111,000 profit

MÅKEN FORLAG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MÅKEN FORLAG AS

Who owns MÅKEN FORLAG AS?

SONJA HELENE DALSETH is the largest registered owner, with 100.0%.

What is the revenue of MÅKEN FORLAG AS?

MÅKEN FORLAG AS had revenue of NOK 623,000 in 2024.

Who is the general manager of MÅKEN FORLAG AS?

Sonja Helene Dalseth is registered as general manager of MÅKEN FORLAG AS.

Where is MÅKEN FORLAG AS based?

MÅKEN FORLAG AS has its business address in Finstadjordet.

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.