biztrac. BETA
COMPANY REGISTER PROFILE
935920558 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Publishing of books

BLUSS FORLAG AS

Org. no. 935920558 Limited company (AS) Ålesund Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 80,000
Operating profit NOK 58,000
Equity NOK 90,000
Incorporated 2025
Share capital NOK 50,000

BLUSS FORLAG AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 935920558. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 2025. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Utvikling, produksjon og salg av bøker og produkter innen for universene skapt i utgitte verk. Selskapet kan også drive annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 80,000 in revenue and NOK 58,000 in operating profit.

Key figures · 2025

Revenue
NOK 80,000
Operating profit
NOK 58,000
Equity
NOK 90,000
Est. value
NOK 247,000

Financial health · 2025

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

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

Who owns BLUSS FORLAG AS?

BLUSS FORLAG AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLUSS FORLAG AS

Who owns BLUSS FORLAG AS?

THOMIR INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BLUSS FORLAG AS?

BLUSS FORLAG AS had revenue of NOK 80,000 in 2025.

Who is the general manager of BLUSS FORLAG AS?

Trine Isaksen Muriaas is registered as general manager of BLUSS FORLAG AS.

Where is BLUSS FORLAG AS based?

BLUSS FORLAG AS has its business address in Ålesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.