BIZTRAC BETA
Sewerage

WELHAVEN TANK & RØR-RENS AS

Org. no. 927405296 Limited company (AS) Sandnes Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 234,000
Equity NOK 54,000
Incorporated 2021
Share capital NOK 30,000

WELHAVEN TANK & RØR-RENS AS is registered as a limited company in Sandnes, Rogaland with organisation number 927405296. The business is classified under sewerage (NACE 37.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Renovasjon, tømming av tanker, åpning av tette rør og andre tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 234,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 234,000
Equity
NOK 54,000
Est. value
NOK 745,000

Financial health · 2025

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

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

Who owns WELHAVEN TANK & RØR-RENS AS?

JARLE MEIER STENE
WELHAVEN TANK & RØR-RENS AS
NOK 1.6m rev. · NOK 234,000 profit

WELHAVEN TANK & RØR-RENS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about WELHAVEN TANK & RØR-RENS AS

Who owns WELHAVEN TANK & RØR-RENS AS?

JARLE MEIER STENE is the largest registered owner, with 50.0%.

What is the revenue of WELHAVEN TANK & RØR-RENS AS?

WELHAVEN TANK & RØR-RENS AS had revenue of NOK 1.6m in 2025.

Who is the general manager of WELHAVEN TANK & RØR-RENS AS?

Andre Meier Stene is registered as general manager of WELHAVEN TANK & RØR-RENS AS.

Where is WELHAVEN TANK & RØR-RENS AS based?

WELHAVEN TANK & RØR-RENS AS has its business address in Sandnes.

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.