BIZTRAC BETA
Industrial product and fashion design activities

PAGAN STUDIO AS

Org. no. 932873192 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 33,000
Operating profit NOK −21,000
Equity NOK 23,000
Incorporated 2024
Share capital NOK 50,000

Signals

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

PAGAN STUDIO AS is registered as a limited company in Bergen, Vestland with organisation number 932873192. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Tilby industridesign, produktdesign og andre tekniske design tjenester, inkludert, men ikke begrenset til, konseptutvikling, 3D-modellering, prototyping, produksjonsovervåking og designrådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 33,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 33,000
Operating profit
NOK −21,000
Equity
NOK 23,000
Est. value
NOK 46,000

Financial health · 2025

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

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

Who owns PAGAN STUDIO AS?

KJETIL HAARR
PAGAN STUDIO AS
NOK 33,000 rev. · NOK −21,000 profit

PAGAN STUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAGAN STUDIO AS

Who owns PAGAN STUDIO AS?

KJETIL HAARR is the largest registered owner, with 100.0%.

What is the revenue of PAGAN STUDIO AS?

PAGAN STUDIO AS had revenue of NOK 33,000 in 2025.

Where is PAGAN STUDIO AS based?

PAGAN STUDIO AS has its business address in Bergen.

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.