BIZTRAC BETA
Wholesale of other household goods

KVALITETSTID AS

Org. no. 917618828 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 8.5m
Operating profit NOK −1.5m
Equity NOK −671,000
Incorporated 2016
Share capital NOK 180,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−671k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,5 mill kr).
  • Nylig endring 2026-05-07 Aksjekapital registrert 2026-05-07.

KVALITETSTID AS is registered as a limited company in Oslo, Oslo with organisation number 917618828. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2016. Registered share capital is NOK 180,000, divided into 125 shares. The company's stated purpose is: “Varehandel.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.5m in revenue and NOK −1.5m in operating profit.

Key figures · 2025

Revenue
NOK 8.5m
Operating profit
NOK −1.5m
Equity
NOK −671,000

Financial health · 2025

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

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

Who owns KVALITETSTID AS?

GEIR JÅSUND AS
KVALITETSTID AS
NOK 8.5m rev. · NOK −1.5m profit

KVALITETSTID AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVALITETSTID AS

Who owns KVALITETSTID AS?

GEIR JÅSUND AS is the largest registered owner, with 100.0%.

What is the revenue of KVALITETSTID AS?

KVALITETSTID AS had revenue of NOK 8.5m in 2025.

Who is the general manager of KVALITETSTID AS?

Geir Jåsund is registered as general manager of KVALITETSTID AS.

Where is KVALITETSTID AS based?

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