BIZTRAC BETA
Intermediation service activities for non-specialised retail sale

STAMPERSTUEN AS

Org. no. 931729438 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 208,000
Operating profit NOK 5,000
Equity NOK −17,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−17k kr).
  • Nylig endring 2026-07-06 Adresseendring registrert 2026-07-06.

STAMPERSTUEN AS is registered as a limited company in Oslo, Oslo with organisation number 931729438. The business is classified under intermediation service activities for non-specialised retail sale (NACE 47.910). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av kunst- og byggemateriale, herunder også vedlikehold og konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 208,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 208,000
Operating profit
NOK 5,000
Equity
NOK −17,000
Est. value
NOK 38,000

Financial health · 2025

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

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

Who owns STAMPERSTUEN AS?

ANDRÉ THORSTENSEN
STAMPERSTUEN AS
NOK 208,000 rev. · NOK 5,000 profit

STAMPERSTUEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAMPERSTUEN AS

Who owns STAMPERSTUEN AS?

ANDRÉ THORSTENSEN is the largest registered owner, with 100.0%.

What is the revenue of STAMPERSTUEN AS?

STAMPERSTUEN AS had revenue of NOK 208,000 in 2025.

Where is STAMPERSTUEN AS based?

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