BIZTRAC BETA
Activities of excursion and event organisers

TINDESKUE AS

Org. no. 930673099 Limited company (AS) Vestnes Incorporated 2023 Active
Ownership graph ↗
Revenue 2023 NOK 8,000
Operating profit NOK 8,000
Equity NOK 32,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.

TINDESKUE AS is registered as a limited company in Vestnes, Møre og Romsdal with organisation number 930673099. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen idrett, friluftsliv, turisme, utdanning, opplevelser og kunnskap. - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2023 financial year, show NOK 8,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2023

Revenue
NOK 8,000
Operating profit
NOK 8,000
Equity
NOK 32,000
Est. value
NOK 48,000

Financial health · 2023

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TINDESKUE AS?

No shareholders are registered for TINDESKUE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TINDESKUE AS

What is the revenue of TINDESKUE AS?

TINDESKUE AS had revenue of NOK 8,000 in 2023.

Who is the general manager of TINDESKUE AS?

Geir Tony Tomren is registered as general manager of TINDESKUE AS.

Where is TINDESKUE AS based?

TINDESKUE AS has its business address in Tomrefjord.

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.