BIZTRAC BETA
Other publishing activities, except software publishing

ALMANAKKFORLAGET AS

Org. no. 914364558 Limited company (AS) Lillestrøm Incorporated 1916 Active
Ownership graph ↗
Revenue 2025 NOK 41.5m
Operating profit NOK 1.9m
Equity NOK 6.7m
Incorporated 1916
Employees 6
Share capital NOK 3.0m

ALMANAKKFORLAGET AS is registered as a limited company in Lillestrøm, Akershus with organisation number 914364558. The business is classified under other publishing activities, except software publishing (NACE 58.190). The company was incorporated in 1916 and has 6 registered employees. Registered share capital is NOK 3.0m, divided into 10000 shares. The company's stated purpose is: “Handel og forlagsvirksomhet, samt enhver virksomhet som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 41.5m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 41.5m
Operating profit
NOK 1.9m
Equity
NOK 6.7m
Est. value
NOK 14.0m

Financial health · 2025

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.4%
Good
Equity as a share of total capital

Who owns ALMANAKKFORLAGET AS?

SCHNEIDER INTERNATIONAL AG
ALMANAKKFORLAGET AS
NOK 41.5m rev. · NOK 1.9m profit

ALMANAKKFORLAGET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALMANAKKFORLAGET AS

Who owns ALMANAKKFORLAGET AS?

SCHNEIDER INTERNATIONAL AG is the largest registered owner, with 100.0%.

What is the revenue of ALMANAKKFORLAGET AS?

ALMANAKKFORLAGET AS had revenue of NOK 41.5m in 2025.

Who is the general manager of ALMANAKKFORLAGET AS?

Hans Olav Hoff is registered as general manager of ALMANAKKFORLAGET AS.

Where is ALMANAKKFORLAGET AS based?

ALMANAKKFORLAGET AS has its business address in Skjetten.

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.