biztrac. BETA
COMPANY REGISTER PROFILE
935624665 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

BÅT OG TRANSPORT AS

Org. no. 935624665 Limited company (AS) Bergen Incorporated 2025 Active
Revenue 2025 NOK 27,000
Operating profit NOK −141,000
Equity NOK −118,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

BÅT OG TRANSPORT AS is registered as a limited company in Bergen, Vestland with organisation number 935624665. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Transport av båter og biler, samt kjøp og salg av båter og biler.”. The most recent filed accounts, for the 2025 financial year, show NOK 27,000 in revenue and NOK −141,000 in operating profit.

Former names: JEHS 32 625 AS

Key figures · 2025

Revenue
NOK 27,000
Operating profit
NOK −141,000
Equity
NOK −118,000

Financial health · 2025

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

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

Who owns BÅT OG TRANSPORT AS?

No shareholders are registered for BÅT OG TRANSPORT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BÅT OG TRANSPORT AS

What is the revenue of BÅT OG TRANSPORT AS?

BÅT OG TRANSPORT AS had revenue of NOK 27,000 in 2025.

Who is the general manager of BÅT OG TRANSPORT AS?

Magne Steindal is registered as general manager of BÅT OG TRANSPORT AS.

Where is BÅT OG TRANSPORT AS based?

BÅT OG TRANSPORT AS has its business address in Mathopen.

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.