BIZTRAC BETA
Activities of adventure companies

KVALØYA HUSKY AS

Org. no. 922645264 Limited company (AS) Tromsø Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 6.0m
Operating profit NOK 1.1m
Equity NOK 1.7m
Incorporated 2019
Employees 7
Share capital NOK 230,000

KVALØYA HUSKY AS is registered as a limited company in Tromsø, Troms with organisation number 922645264. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2019 and has 7 registered employees. Registered share capital is NOK 230,000, divided into 230 shares. The company's stated purpose is: “Drive aktivitetstilbud innen naturopplevelser, herunder hundesledekjøring. Selskapet skal også drive med salg av hunder, hundeutstyr og hundefòr, samt delta i konkurransekjøring både nasjonalt og internasjonalt.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.0m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 6.0m
Operating profit
NOK 1.1m
Equity
NOK 1.7m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns KVALØYA HUSKY AS?

TOMMY THEODORSEN
KVALØYA HUSKY AS
NOK 6.0m rev. · NOK 1.1m profit

KVALØYA HUSKY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVALØYA HUSKY AS

Who owns KVALØYA HUSKY AS?

TOMMY THEODORSEN is the largest registered owner, with 50.0%.

What is the revenue of KVALØYA HUSKY AS?

KVALØYA HUSKY AS had revenue of NOK 6.0m in 2024.

Who is the general manager of KVALØYA HUSKY AS?

Tommy Theodorsen is registered as general manager of KVALØYA HUSKY AS.

Where is KVALØYA HUSKY AS based?

KVALØYA HUSKY AS has its business address in Straumsbukta.

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.