biztrac. BETA
COMPANY REGISTER PROFILE
935813700 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of tour guides

VETLESKOG AS

Org. no. 935813700 Limited company (AS) Luster Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 19,000
Operating profit NOK −25,000
Equity NOK −25,000
Incorporated 2025
Share capital NOK 40,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−25k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).

VETLESKOG AS is registered as a limited company in Luster, Vestland with organisation number 935813700. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2025. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Reiselivsvirksomhet, kjøp, salg og utleie av eiendom og verdipapier.”. The most recent filed accounts, for the 2025 financial year, show NOK 19,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 19,000
Operating profit
NOK −25,000
Equity
NOK −25,000

Financial health · 2025

Liquidity
-0.49
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
303.2%
Weak
Equity as a share of total capital

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

Who owns VETLESKOG AS?

VETLESKOG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about VETLESKOG AS

Who owns VETLESKOG AS?

Mathias Ramsland Rønnestad is the largest registered owner, with 25.0%.

What is the revenue of VETLESKOG AS?

VETLESKOG AS had revenue of NOK 19,000 in 2025.

Who is the general manager of VETLESKOG AS?

Lars Skrede Kvåle is registered as general manager of VETLESKOG AS.

Where is VETLESKOG AS based?

VETLESKOG AS has its business address in Hafslo.

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.