BIZTRAC BETA
Web search portal activities

ZUPERHOME AS

Org. no. 933303527 Limited company (AS) Kristiansand Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 100,000
Operating profit NOK −23,000
Equity NOK 7,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).
  • Nylig endring 2026-06-25 Adresseendring registrert 2026-06-25.

ZUPERHOME AS is registered as a limited company in Kristiansand, Agder with organisation number 933303527. The business is classified under web search portal activities (NACE 63.910). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive web-portaler, inkludert, men ikke begrenset til, å tilby nettplattformer for e-handel, sosiale nettverk, digitalt innhold og andre relaterte tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 100,000 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 100,000
Operating profit
NOK −23,000
Equity
NOK 7,000
Est. value
NOK 172,000

Financial health · 2024

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

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

Who owns ZUPERHOME AS?

BERGASTØLEN HOLDNING AS
ZUPERHOME AS
NOK 100,000 rev. · NOK −23,000 profit

ZUPERHOME AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ZUPERHOME AS

Who owns ZUPERHOME AS?

BERGASTØLEN HOLDNING AS is the largest registered owner, with 50.0%.

What is the revenue of ZUPERHOME AS?

ZUPERHOME AS had revenue of NOK 100,000 in 2024.

Where is ZUPERHOME AS based?

ZUPERHOME AS has its business address in Kristiansand S.

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.