BIZTRAC BETA
Site preparation

ROY-YNGVE THOMASSEN AS

Org. no. 890024432 Limited company (AS) Alta Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 55.7m
Operating profit NOK −1.1m
Equity NOK 9.4m
Incorporated 2006
Employees 41
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,1 mill kr).

ROY-YNGVE THOMASSEN AS is registered as a limited company in Alta, Finnmark with organisation number 890024432. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2006 and has 41 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Maskinentreprenørvirksomhet og annet som måtte falle naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 55.7m in revenue and NOK −1.1m in operating profit.

Key figures · 2025

Revenue
NOK 55.7m
Operating profit
NOK −1.1m
Equity
NOK 9.4m
Est. value
NOK 18.4m

Financial health · 2025

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

Who owns ROY-YNGVE THOMASSEN AS?

RYT HOLDING AS
ROY-YNGVE THOMASSEN AS
NOK 55.7m rev. · NOK −1.1m profit

ROY-YNGVE THOMASSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROY-YNGVE THOMASSEN AS

Who owns ROY-YNGVE THOMASSEN AS?

RYT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ROY-YNGVE THOMASSEN AS?

ROY-YNGVE THOMASSEN AS had revenue of NOK 55.7m in 2025.

Who is the general manager of ROY-YNGVE THOMASSEN AS?

Roy-Yngve Thomassen is registered as general manager of ROY-YNGVE THOMASSEN AS.

Where is ROY-YNGVE THOMASSEN AS based?

ROY-YNGVE THOMASSEN AS has its business address in Alta.

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.