BIZTRAC BETA
Leasing of intellectual property and similar products, except copyrighted works

SCUTI AS

Org. no. 915713599 Limited company (AS) Verdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 4.4m
Equity NOK 22.3m
Incorporated 2015
Share capital NOK 82,000

SCUTI AS is registered as a limited company in Verdal, Trøndelag with organisation number 915713599. The business is classified under leasing of intellectual property and similar products, except copyrighted works (NACE 77.400). The company was incorporated in 2015. Registered share capital is NOK 82,000, divided into 246454 shares. The company's stated purpose is: “Eie og videreutvikle patenter og rettigheter og å være et investeringsselskap, herunder investering i aksjer, andeler i selskaper, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 4.4m in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 4.4m
Equity
NOK 22.3m
Est. value
NOK 29.3m

Financial health · 2025

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

Who owns SCUTI AS?

SAVERTO FRANCE SAS
SCUTI AS
NOK 4.8m rev. · NOK 4.4m profit

SCUTI AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SCUTI AS er morselskap for 2 datterselskaper:

Frequently asked questions about SCUTI AS

Who owns SCUTI AS?

SAVERTO FRANCE SAS is the largest registered owner, with 100.0%.

What is the revenue of SCUTI AS?

SCUTI AS had revenue of NOK 4.8m in 2025.

Who is the general manager of SCUTI AS?

Frode Resve is registered as general manager of SCUTI AS.

Where is SCUTI AS based?

SCUTI AS has its business address in Verdal.

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.