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

LILLESAND EXPLORER AS

Org. no. 920741797 Limited company (AS) Lillesand Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 161,000
Operating profit NOK −8,000
Equity NOK 273,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

LILLESAND EXPLORER AS is registered as a limited company in Lillesand, Agder with organisation number 920741797. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å tilby utforskende opplevelser i Lillesand og omegn gjennom guiding, instruering, utleie og opplæring.”. The most recent filed accounts, for the 2025 financial year, show NOK 161,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 161,000
▼ −56 %
Operating profit
NOK −8,000
▼ −108 %
Equity
NOK 273,000
▲ +4 %
Est. value
NOK 234,000

Financial health · 2025

Liquidity
4.99
Very good
Current assets ÷ current liabilities
Profitability
-2.2%
Not satisfactory
Return on total assets
Solidity
87.5%
Very good
Equity as a share of total capital

Who owns LILLESAND EXPLORER AS?

LILLESAND EXPLORER AS
NOK 161,000 rev. · NOK −8,000 profit

LILLESAND EXPLORER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLESAND EXPLORER AS

Who owns LILLESAND EXPLORER AS?

Johannes Myhre Vallesverd is the largest registered owner, with 100.0%.

What is the revenue of LILLESAND EXPLORER AS?

LILLESAND EXPLORER AS had revenue of NOK 161,000 in 2025.

Where is LILLESAND EXPLORER AS based?

LILLESAND EXPLORER AS has its business address in Lillesand.

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.