BIZTRAC BETA
Other publishing activities, except software publishing

EX LIBRIS FORLAG AS

Org. no. 981037316 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 119,000
Incorporated 1999
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EX LIBRIS FORLAG AS is registered as a limited company in Oslo, Oslo with organisation number 981037316. The business is classified under other publishing activities, except software publishing (NACE 58.190). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forlagsvirksomhet, handel og produksjon og alt som hermed står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 119,000
Est. value
NOK 217,000

Financial health · 2025

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

Who owns EX LIBRIS FORLAG AS?

CAPPELEN DAMM AS
EX LIBRIS FORLAG AS
NOK 0 rev. · NOK 0 profit

EX LIBRIS FORLAG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

EX LIBRIS FORLAG AS er morselskap for 35 datterselskaper:

Frequently asked questions about EX LIBRIS FORLAG AS

Who owns EX LIBRIS FORLAG AS?

CAPPELEN DAMM AS is the largest registered owner, with 100.0%.

What is the revenue of EX LIBRIS FORLAG AS?

EX LIBRIS FORLAG AS had revenue of NOK 0 in 2025.

Where is EX LIBRIS FORLAG AS based?

EX LIBRIS 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.