biztrac. BETA
COMPANY REGISTER PROFILE
933808726 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other education activities

BÅTFØRERPRØVEN VR AS

Org. no. 933808726 Limited company (AS) Risør Incorporated 2024 Active
Revenue 2025 NOK 111,000
Operating profit NOK −16,000
Equity NOK −19,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−19k kr).

BÅTFØRERPRØVEN VR AS is registered as a limited company in Risør, Agder with organisation number 933808726. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Undervise i maritime aktiviteter med bruk av VR teknologi, eks: båtførerprøven.”. The most recent filed accounts, for the 2025 financial year, show NOK 111,000 in revenue and NOK −16,000 in operating profit.

Former names: MARITIM GLEDE AS

Key figures · 2025

Revenue
NOK 111,000
Operating profit
NOK −16,000
▲ +52 %
Equity
NOK −19,000
▼ −518 %

Financial health · 2025

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

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

Who owns BÅTFØRERPRØVEN VR AS?

BÅTFØRERPRØVEN VR AS
NOK 111,000 rev. · NOK −16,000 profit

BÅTFØRERPRØVEN VR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BÅTFØRERPRØVEN VR AS

Who owns BÅTFØRERPRØVEN VR AS?

Eivind Nicander is the largest registered owner, with 100.0%.

What is the revenue of BÅTFØRERPRØVEN VR AS?

BÅTFØRERPRØVEN VR AS had revenue of NOK 111,000 in 2025.

Where is BÅTFØRERPRØVEN VR AS based?

BÅTFØRERPRØVEN VR AS has its business address in Risør.

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.