BIZTRAC BETA
Publishing of books

ART PRO FORLAG AS

Org. no. 958201141 Limited company (AS) Lier Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 676,000
Operating profit NOK −109,000
Equity NOK 571,000
Incorporated 1990
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−109k kr).

ART PRO FORLAG AS is registered as a limited company in Lier, Buskerud with organisation number 958201141. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Handel, konsulentvirksomhet, finans- og assuranse- tjenester, forlagsdrift, samt hva hermed står i forbindelse og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 676,000 in revenue and NOK −109,000 in operating profit.

Key figures · 2025

Revenue
NOK 676,000
Operating profit
NOK −109,000
Equity
NOK 571,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns ART PRO FORLAG AS?

TROND BIRGER OLSEN
ART PRO FORLAG AS
NOK 676,000 rev. · NOK −109,000 profit

ART PRO FORLAG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ART PRO FORLAG AS

Who owns ART PRO FORLAG AS?

TROND BIRGER OLSEN is the largest registered owner, with 100.0%.

What is the revenue of ART PRO FORLAG AS?

ART PRO FORLAG AS had revenue of NOK 676,000 in 2025.

Who is the general manager of ART PRO FORLAG AS?

Trond Birger Olsen is registered as general manager of ART PRO FORLAG AS.

Where is ART PRO FORLAG AS based?

ART PRO FORLAG AS has its business address in Gullaug.

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.