BIZTRAC BETA
Publishing of books

AGALAUS FORLAG AS

Org. no. 918144080 Limited company (AS) Tromsø Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 10,000
Operating profit NOK −19,000
Equity NOK 96,000
Incorporated 2016
Share capital NOK 40,000

Signals

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

AGALAUS FORLAG AS is registered as a limited company in Tromsø, Troms with organisation number 918144080. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 2016. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Forlagsvirksomhet. Salg av bøker, trykte publikasjoner og bilder.”. The most recent filed accounts, for the 2024 financial year, show NOK 10,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 10,000
Operating profit
NOK −19,000
Equity
NOK 96,000
Est. value
NOK 61,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AGALAUS FORLAG AS?

CHRISTINE KRISTOFFERSEN HANSEN
AGALAUS FORLAG AS
NOK 10,000 rev. · NOK −19,000 profit

AGALAUS FORLAG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AGALAUS FORLAG AS

Who owns AGALAUS FORLAG AS?

CHRISTINE KRISTOFFERSEN HANSEN is the largest registered owner, with 50.0%.

What is the revenue of AGALAUS FORLAG AS?

AGALAUS FORLAG AS had revenue of NOK 10,000 in 2024.

Who is the general manager of AGALAUS FORLAG AS?

Christine Kristoffersen Hansen is registered as general manager of AGALAUS FORLAG AS.

Where is AGALAUS FORLAG AS based?

AGALAUS FORLAG AS has its business address in Tromsø.

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.