BIZTRAC BETA
Computer programming activities

PRINT.PAGE AS

Org. no. 929542649 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −122,000
Equity NOK 26,000
Incorporated 2022
Share capital NOK 300,000

Signals

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

PRINT.PAGE AS is registered as a limited company in Oslo, Oslo with organisation number 929542649. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 300,000, divided into 4000000 shares. The company's stated purpose is: “Program-, internett- og APP-utvikling og design, rådgivning og salg av produkter og tjenester rettet mot trykkindustrien, samt annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −122,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −122,000
Equity
NOK 26,000
Est. value
NOK 47,000

Financial health · 2025

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

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

Who owns PRINT.PAGE AS?

TANGERIN AS
PRINT.PAGE AS
NOK 0 rev. · NOK −122,000 profit

PRINT.PAGE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRINT.PAGE AS

Who owns PRINT.PAGE AS?

TANGERIN AS is the largest registered owner, with 95.0%.

What is the revenue of PRINT.PAGE AS?

PRINT.PAGE AS had revenue of NOK 0 in 2025.

Who is the general manager of PRINT.PAGE AS?

Kurt Patrik Knutsson is registered as general manager of PRINT.PAGE AS.

Where is PRINT.PAGE AS based?

PRINT.PAGE 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.