BIZTRAC BETA
Repair and maintenance of motor vehicles

BROTORVET BIL OG BÅTPLEIE AS

Org. no. 912539806 Limited company (AS) Bamble Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 114,000
Equity NOK −107,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

BROTORVET BIL OG BÅTPLEIE AS is registered as a limited company in Bamble, Telemark with organisation number 912539806. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Vask og pleie av bil og båt samt annet som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 114,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 114,000
Equity
NOK −107,000
Est. value
NOK 852,000

Financial health · 2024

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.8%
Weak
Equity as a share of total capital

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

Who owns BROTORVET BIL OG BÅTPLEIE AS?

LULZIM RAMADANI
BROTORVET BIL OG BÅTPLEIE AS
NOK 2.1m rev. · NOK 114,000 profit

BROTORVET BIL OG BÅTPLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROTORVET BIL OG BÅTPLEIE AS

Who owns BROTORVET BIL OG BÅTPLEIE AS?

LULZIM RAMADANI is the largest registered owner, with 100.0%.

What is the revenue of BROTORVET BIL OG BÅTPLEIE AS?

BROTORVET BIL OG BÅTPLEIE AS had revenue of NOK 2.1m in 2024.

Where is BROTORVET BIL OG BÅTPLEIE AS based?

BROTORVET BIL OG BÅTPLEIE AS has its business address in Stathelle.

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.