BIZTRAC BETA
Retail sale of games and toys

HVITÅS LEIKER AS

Org. no. 912015874 Limited company (AS) Midt-Telemark Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 69,000
Equity NOK 2.1m
Incorporated 2013
Employees 6
Share capital NOK 250,000

HVITÅS LEIKER AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 912015874. The business is classified under retail sale of games and toys (NACE 47.640). The company was incorporated in 2013 and has 6 registered employees. Registered share capital is NOK 250,000, divided into 100 shares. The company's stated purpose is: “Butikkhandel med spill og leiker, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 69,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK 69,000
Equity
NOK 2.1m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns HVITÅS LEIKER AS?

ANNY HVITÅS
HVITÅS LEIKER AS
NOK 6.1m rev. · NOK 69,000 profit

HVITÅS LEIKER AS has 4 registered shareholders:

All shareholders and roles →

Which companies does HVITÅS LEIKER AS own?

HVITÅS LEIKER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HVITÅS LEIKER AS

Who owns HVITÅS LEIKER AS?

ANNY HVITÅS is the largest registered owner, with 34.0%.

What is the revenue of HVITÅS LEIKER AS?

HVITÅS LEIKER AS had revenue of NOK 6.1m in 2025.

Who is the general manager of HVITÅS LEIKER AS?

Anny Hvitås is registered as general manager of HVITÅS LEIKER AS.

Where is HVITÅS LEIKER AS based?

HVITÅS LEIKER AS has its business address in Bø I Telemark.

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.