BIZTRAC BETA
Other tour operator activities

RESYME VEST AS

Org. no. 975795322 Limited company (AS) Steinkjer Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 107,000
Operating profit NOK 3,000
Equity NOK 158,000
Incorporated 1995
Share capital NOK 275,000

RESYME VEST AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 975795322. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 1995. Registered share capital is NOK 275,000, divided into 2750 shares. The company's stated purpose is: “Reiseliv og relaterte næringer, arrangement, finansielle tjenester, investeringsvirksomhet, samt delta i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 107,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 107,000
Operating profit
NOK 3,000
Equity
NOK 158,000
Est. value
NOK 96,000

Financial health · 2025

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

Who owns RESYME VEST AS?

HELGE RISNES NYHUS
RESYME VEST AS
NOK 107,000 rev. · NOK 3,000 profit

RESYME VEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RESYME VEST AS own?

RESYME VEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RESYME VEST AS

Who owns RESYME VEST AS?

HELGE RISNES NYHUS is the largest registered owner, with 100.0%.

What is the revenue of RESYME VEST AS?

RESYME VEST AS had revenue of NOK 107,000 in 2025.

Who is the general manager of RESYME VEST AS?

Henning-Oddleiv Nyhus is registered as general manager of RESYME VEST AS.

Where is RESYME VEST AS based?

RESYME VEST AS has its business address in Steinkjer.

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.