BIZTRAC BETA
Other cleaning activities

TANK OG TRAILERVASK AS

Org. no. 832031232 Limited company (AS) Porsgrunn Incorporated 1982 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 824,000
Equity NOK 2.0m
Incorporated 1982
Employees 6
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TANK OG TRAILERVASK AS is registered as a limited company in Porsgrunn, Telemark with organisation number 832031232. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 1982 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Innvendig og utvendig rengjøring av bulkbiler og andre kjøretøyer, samt hva som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 824,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 824,000
Equity
NOK 2.0m
Est. value
NOK 4.0m

Financial health · 2024

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.8%
Good
Equity as a share of total capital

Who owns TANK OG TRAILERVASK AS?

L GRØNAASEN TRANSPORT AS
TANK OG TRAILERVASK AS
NOK 10.1m rev. · NOK 824,000 profit

TANK OG TRAILERVASK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANK OG TRAILERVASK AS

Who owns TANK OG TRAILERVASK AS?

L GRØNAASEN TRANSPORT AS is the largest registered owner, with 100.0%.

What is the revenue of TANK OG TRAILERVASK AS?

TANK OG TRAILERVASK AS had revenue of NOK 10.1m in 2024.

Where is TANK OG TRAILERVASK AS based?

TANK OG TRAILERVASK AS has its business address in Porsgrunn.

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.