BIZTRAC BETA
Manufacture of other textiles n.e.c.

PRINTBERRY AS

Org. no. 939857931 Limited company (AS) Oslo Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK −113,000
Equity NOK −1.4m
Incorporated 1986
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−113k kr).

PRINTBERRY AS is registered as a limited company in Oslo, Oslo with organisation number 939857931. The business is classified under manufacture of other textiles n.e.c. (NACE 13.990). The company was incorporated in 1986. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg og trykk av reklameartikler og tekstiler, samt det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK −113,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK −113,000
Equity
NOK −1.4m

Financial health · 2024

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

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

Who owns PRINTBERRY AS?

MERCHBERRY AS
PRINTBERRY AS
NOK 3.4m rev. · NOK −113,000 profit

PRINTBERRY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PRINTBERRY AS

Who owns PRINTBERRY AS?

MERCHBERRY AS is the largest registered owner, with 100.0%.

What is the revenue of PRINTBERRY AS?

PRINTBERRY AS had revenue of NOK 3.4m in 2024.

Who is the general manager of PRINTBERRY AS?

Even Bø Ruud is registered as general manager of PRINTBERRY AS.

Where is PRINTBERRY AS based?

PRINTBERRY 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.