BIZTRAC BETA
Arts creation activities in literature

KAPRIFOL LITTERATUR AS

Org. no. 935182972 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 334,000
Operating profit NOK 2,000
Equity NOK 25,000
Incorporated 2025
Share capital NOK 30,000

KAPRIFOL LITTERATUR AS is registered as a limited company in Oslo, Oslo with organisation number 935182972. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forfattervirksomhet. Skal skrive bøker og holde skrivekurs.”. The most recent filed accounts, for the 2025 financial year, show NOK 334,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 334,000
Operating profit
NOK 2,000
Equity
NOK 25,000
Est. value
NOK 21,000

Financial health · 2025

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.7%
Weak
Equity as a share of total capital

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

Who owns KAPRIFOL LITTERATUR AS?

ANNE LOUISE MORSETH-NORDBRYHN
KAPRIFOL LITTERATUR AS
NOK 334,000 rev. · NOK 2,000 profit

KAPRIFOL LITTERATUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAPRIFOL LITTERATUR AS

Who owns KAPRIFOL LITTERATUR AS?

ANNE LOUISE MORSETH-NORDBRYHN is the largest registered owner, with 100.0%.

What is the revenue of KAPRIFOL LITTERATUR AS?

KAPRIFOL LITTERATUR AS had revenue of NOK 334,000 in 2025.

Who is the general manager of KAPRIFOL LITTERATUR AS?

Anne Louise Morseth-Nordbryhn is registered as general manager of KAPRIFOL LITTERATUR AS.

Where is KAPRIFOL LITTERATUR AS based?

KAPRIFOL LITTERATUR 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.