BIZTRAC BETA
Publishing of books

FLOSSHATT FORLAG AS

Org. no. 935452996 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK −35,000
Equity NOK −12,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−12k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).

FLOSSHATT FORLAG AS is registered as a limited company in Oslo, Oslo with organisation number 935452996. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Bokutgivelser og annen kultur- og kunnskapsformidling.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK −35,000
Equity
NOK −12,000

Financial health · 2025

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

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

Who owns FLOSSHATT FORLAG AS?

KARIN KILDE
FLOSSHATT FORLAG AS
NOK 16,000 rev. · NOK −35,000 profit

FLOSSHATT FORLAG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLOSSHATT FORLAG AS

Who owns FLOSSHATT FORLAG AS?

KARIN KILDE is the largest registered owner, with 66.7%.

What is the revenue of FLOSSHATT FORLAG AS?

FLOSSHATT FORLAG AS had revenue of NOK 16,000 in 2025.

Who is the general manager of FLOSSHATT FORLAG AS?

Karin Kilde is registered as general manager of FLOSSHATT FORLAG AS.

Where is FLOSSHATT FORLAG AS based?

FLOSSHATT FORLAG AS has its business address in Oslo.

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.