biztrac. BETA
COMPANY REGISTER PROFILE
980797309 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Hotels and similar accommodation

SKARVET AS

Org. no. 980797309 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 394.5m
Operating profit NOK 14.5m
Equity NOK 21.4m
Incorporated 1999
Employees 316
Share capital NOK 100,000

SKARVET AS is registered as a limited company in Oslo, Oslo with organisation number 980797309. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 1999 and has 316 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er å forestå drift av hoteller, restauranter, kurs og konferansesentre, eie og leie ut eiendom samt annen virksomhet i tilknytning til dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 394.5m in revenue and NOK 14.5m in operating profit.

Former names: SKARVEN AS

Key figures · 2025

Revenue
NOK 394.5m
▲ +11 %
Operating profit
NOK 14.5m
▲ +4061 %
Equity
NOK 21.4m
▲ +20 %
Est. value
NOK 55.9m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
19.8%
Very good
Return on total assets
Solidity
23.8%
Good
Equity as a share of total capital

Who owns SKARVET AS?

SKARVET AS
NOK 394.5m rev. · NOK 14.5m profit

SKARVET AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SKARVET AS er morselskap for 65 datterselskaper:

Frequently asked questions about SKARVET AS

Who owns SKARVET AS?

THON HOTELS AS is the largest registered owner, with 100.0%.

What is the revenue of SKARVET AS?

SKARVET AS had revenue of NOK 394.5m in 2025.

Where is SKARVET AS based?

SKARVET AS has its business address in Oslo.

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.