BIZTRAC BETA
Other tour operator activities

LEPSØE REISER AS

Org. no. 927511266 Limited company (AS) Tønsberg Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 525,000
Operating profit NOK −21,000
Equity NOK 41,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).
  • Nylig endring 2026-02-23 Adresseendring registrert 2026-02-23.

LEPSØE REISER AS is registered as a limited company in Tønsberg, Vestfold with organisation number 927511266. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Reisearrangørvirksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 525,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 525,000
Operating profit
NOK −21,000
Equity
NOK 41,000
Est. value
NOK 354,000

Financial health · 2025

Liquidity
1.48
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.6%
Weak
Equity as a share of total capital

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

Who owns LEPSØE REISER AS?

GRY LEPSØE
LEPSØE REISER AS
NOK 525,000 rev. · NOK −21,000 profit

LEPSØE REISER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEPSØE REISER AS

Who owns LEPSØE REISER AS?

GRY LEPSØE is the largest registered owner, with 100.0%.

What is the revenue of LEPSØE REISER AS?

LEPSØE REISER AS had revenue of NOK 525,000 in 2025.

Who is the general manager of LEPSØE REISER AS?

Gry Lepsøe is registered as general manager of LEPSØE REISER AS.

Where is LEPSØE REISER AS based?

LEPSØE REISER AS has its business address in Tønsberg.

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.