biztrac. BETA
COMPANY REGISTER PROFILE
992403446 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

ØYA BILTEKNISKE AS

Org. no. 992403446 Limited company (AS) Vefsn Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 7.4m
Operating profit NOK 629,000
Equity NOK 2.8m
Incorporated 2008
Employees 6
Share capital NOK 100,000

ØYA BILTEKNISKE AS is registered as a limited company in Vefsn, Nordland with organisation number 992403446. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2008 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Reparasjon, service og vedlikehold av motorkjøretøyer samt tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.4m in revenue and NOK 629,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.4m
▲ +17 %
Operating profit
NOK 629,000
▲ +34 %
Equity
NOK 2.8m
▲ +21 %
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
2.44
Very good
Current assets ÷ current liabilities
Profitability
14.4%
Good
Return on total assets
Solidity
59.6%
Very good
Equity as a share of total capital

Who owns ØYA BILTEKNISKE AS?

ØYA BILTEKNISKE AS
NOK 7.4m rev. · NOK 629,000 profit

ØYA BILTEKNISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYA BILTEKNISKE AS

Who owns ØYA BILTEKNISKE AS?

Kim Vidar Hånes is the largest registered owner, with 100.0%.

What is the revenue of ØYA BILTEKNISKE AS?

ØYA BILTEKNISKE AS had revenue of NOK 7.4m in 2025.

Who is the general manager of ØYA BILTEKNISKE AS?

Kim Vidar Hånes is registered as general manager of ØYA BILTEKNISKE AS.

Where is ØYA BILTEKNISKE AS based?

ØYA BILTEKNISKE AS has its business address in Mosjøen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.