BIZTRAC BETA
Industrial product and fashion design activities

PAAPUR AS

Org. no. 933344657 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −45,000
Equity NOK −15,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−15k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−45k kr).

PAAPUR AS is registered as a limited company in Oslo, Oslo with organisation number 933344657. 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 30,000, divided into 300 shares. The company's stated purpose is: “Designe tekstiler som pledd, tepper, håndklær, t -skjorter og lignende, og selge gjennom nettbutikk og fysiske butikker.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −45,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −45,000
Equity
NOK −15,000

Financial health · 2024

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

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

Who owns PAAPUR AS?

WALLSTORIES AS
PAAPUR AS
NOK 0 rev. · NOK −45,000 profit

PAAPUR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PAAPUR AS

Who owns PAAPUR AS?

WALLSTORIES AS is the largest registered owner, with 66.7%.

What is the revenue of PAAPUR AS?

PAAPUR AS had revenue of NOK 0 in 2024.

Who is the general manager of PAAPUR AS?

Fredrik Raaholt Strømme is registered as general manager of PAAPUR AS.

Where is PAAPUR AS based?

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