BIZTRAC BETA
Retail sale of second-hand goods

CAPPELENS FORSLAG AS

Org. no. 996963063 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 590,000
Operating profit NOK 25,000
Equity NOK −43,000
Incorporated 2011
Share capital NOK 140,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−43k kr).

CAPPELENS FORSLAG AS is registered as a limited company in Oslo, Oslo with organisation number 996963063. The business is classified under retail sale of second-hand goods (NACE 47.790). The company was incorporated in 2011. Registered share capital is NOK 140,000, divided into 140 shares. The company's stated purpose is: “Butikk/nettbutikkhandel av nye og antikvariske bøker, vinylplater, t-skjorter, kunst, kort og snurrepipperier kulturelle arrangementer, servering m.m.”. The most recent filed accounts, for the 2024 financial year, show NOK 590,000 in revenue and NOK 25,000 in operating profit.

Key figures · 2024

Revenue
NOK 590,000
Operating profit
NOK 25,000
Equity
NOK −43,000
Est. value
NOK 173,000

Financial health · 2024

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-22.7%
Weak
Equity as a share of total capital

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

Who owns CAPPELENS FORSLAG AS?

PIL CHRISTIAN CAPPELEN SMITH
CAPPELENS FORSLAG AS
NOK 590,000 rev. · NOK 25,000 profit

CAPPELENS FORSLAG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about CAPPELENS FORSLAG AS

Who owns CAPPELENS FORSLAG AS?

PIL CHRISTIAN CAPPELEN SMITH is the largest registered owner, with 42.9%.

What is the revenue of CAPPELENS FORSLAG AS?

CAPPELENS FORSLAG AS had revenue of NOK 590,000 in 2024.

Where is CAPPELENS FORSLAG AS based?

CAPPELENS FORSLAG 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.