BIZTRAC BETA
Repair and maintenance of household appliances and home and garden equipment

HVITEVARESERVICE AS

Org. no. 980924254 Limited company (AS) Øvre Eiker Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK 522,000
Equity NOK 2.9m
Incorporated 1999
Share capital NOK 100,000

HVITEVARESERVICE AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 980924254. The business is classified under repair and maintenance of household appliances and home and garden equipment (NACE 95.220). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Reparasjon og salg av elektriske husholdningsartikler og alt som står i forbindelse med dette - herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK 522,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK 522,000
Equity
NOK 2.9m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns HVITEVARESERVICE AS?

JARLE RØED
HVITEVARESERVICE AS
NOK 6.3m rev. · NOK 522,000 profit

HVITEVARESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HVITEVARESERVICE AS

Who owns HVITEVARESERVICE AS?

JARLE RØED is the largest registered owner, with 100.0%.

What is the revenue of HVITEVARESERVICE AS?

HVITEVARESERVICE AS had revenue of NOK 6.3m in 2024.

Who is the general manager of HVITEVARESERVICE AS?

Jarle Røed is registered as general manager of HVITEVARESERVICE AS.

Where is HVITEVARESERVICE AS based?

HVITEVARESERVICE AS has its business address in Vestfossen.

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.