biztrac. BETA
COMPANY REGISTER PROFILE
925043680 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other household goods

LONGBOAT SOLUTIONS AS

Org. no. 925043680 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −314,000
Equity NOK 448,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−314k kr).
  • Nylig endring 2026-04-25 Adresseendring registrert 2026-04-25.

LONGBOAT SOLUTIONS AS is registered as a limited company in Oslo, Oslo with organisation number 925043680. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 2 shares. The company's stated purpose is: “Tilby tjenester innen Risk management, herunder kjøp og salg av produkter og utstyr innen helse, miljø og sikkerhet. Longboat Solutions AS kan også tilby logistikk støtte, rådgivning og ledelse. Longboat Solutions AS kan tilby personlig beskyttelsesutstyr, herunder smittevernutstyr for privatpersoner og helsepersonell.”.

Key figures · 2025

Operating profit
NOK −314,000
▼ −44 %
Equity
NOK 448,000
▼ −40 %
Est. value
NOK 560,000

Financial health · 2025

Liquidity
2.02
Very good
Current assets ÷ current liabilities
Profitability
-31.3%
Not satisfactory
Return on total assets
Solidity
50.6%
Very good
Equity as a share of total capital

Who owns LONGBOAT SOLUTIONS AS?

BULLWEILER RISK LTD TC
LONGBOAT SOLUTIONS AS
· NOK −314,000 profit

LONGBOAT SOLUTIONS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LONGBOAT SOLUTIONS AS

Who owns LONGBOAT SOLUTIONS AS?

BULLWEILER RISK LTD is the largest registered owner, with 50.0%.

Where is LONGBOAT SOLUTIONS AS based?

LONGBOAT SOLUTIONS AS has its business address in Oslo.

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.