BIZTRAC BETA
Rental and operating of own or leased real estate

FLYUM DE CABO ROIG AS

Org. no. 997146859 Limited company (AS) Stjørdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 66,000
Operating profit NOK 8,000
Equity NOK 744,000
Incorporated 2011
Share capital NOK 900,000

FLYUM DE CABO ROIG AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 997146859. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 900,000, divided into 900 shares. The company's stated purpose is: “Erverv, oppføring og drift av fast eiendom, samt gjennom eierinteresser å delta i andre selskap som har eiendomsdrift eller annen forretningsvirksomhet som formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 66,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 66,000
Operating profit
NOK 8,000
Equity
NOK 744,000
Est. value
NOK 525,000

Financial health · 2024

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

Who owns FLYUM DE CABO ROIG AS?

DAGFINN KASSETH
FLYUM DE CABO ROIG AS
NOK 66,000 rev. · NOK 8,000 profit

FLYUM DE CABO ROIG AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLYUM DE CABO ROIG AS

Who owns FLYUM DE CABO ROIG AS?

DAGFINN KASSETH is the largest registered owner, with 16.7%.

What is the revenue of FLYUM DE CABO ROIG AS?

FLYUM DE CABO ROIG AS had revenue of NOK 66,000 in 2024.

Who is the general manager of FLYUM DE CABO ROIG AS?

Arve Solum is registered as general manager of FLYUM DE CABO ROIG AS.

Where is FLYUM DE CABO ROIG AS based?

FLYUM DE CABO ROIG AS has its business address in Stjørdal.

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.