BIZTRAC BETA
Repair and maintenance of personal and household goods n.e.c.

VANNSCOOTER SERVICE AS

Org. no. 923651411 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 234,000
Equity NOK 1.9m
Incorporated 2019
Share capital NOK 30,000

VANNSCOOTER SERVICE AS is registered as a limited company in Drammen, Buskerud with organisation number 923651411. The business is classified under repair and maintenance of personal and household goods n.e.c. (NACE 95.290). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Vedlikehold, reparasjon, tuning og utleie av vannscootere, samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 234,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 234,000
Equity
NOK 1.9m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns VANNSCOOTER SERVICE AS?

PATRICK THRONDSEN
VANNSCOOTER SERVICE AS
NOK 2.7m rev. · NOK 234,000 profit

VANNSCOOTER SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VANNSCOOTER SERVICE AS

Who owns VANNSCOOTER SERVICE AS?

PATRICK THRONDSEN is the largest registered owner, with 100.0%.

What is the revenue of VANNSCOOTER SERVICE AS?

VANNSCOOTER SERVICE AS had revenue of NOK 2.7m in 2024.

Who is the general manager of VANNSCOOTER SERVICE AS?

Patrick Throndsen is registered as general manager of VANNSCOOTER SERVICE AS.

Where is VANNSCOOTER SERVICE AS based?

VANNSCOOTER SERVICE AS has its business address in Drammen.

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.