BIZTRAC BETA
Other technical consultancy

VANNTEKNIKK SØR AS

Org. no. 923097678 Limited company (AS) Grimstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK −410,000
Equity NOK 679,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−410k kr).

VANNTEKNIKK SØR AS is registered as a limited company in Grimstad, Agder with organisation number 923097678. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Trykktest, spyling, kontroll av borehull, brønner og alt som naturlig hører til dette, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK −410,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK −410,000
Equity
NOK 679,000
Est. value
NOK 4.8m

Financial health · 2024

Liquidity
1.84
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.6%
Very good
Equity as a share of total capital

Who owns VANNTEKNIKK SØR AS?

BERNT IVAR GILJE ANDERSEN
VANNTEKNIKK SØR AS
NOK 4.3m rev. · NOK −410,000 profit

VANNTEKNIKK SØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VANNTEKNIKK SØR AS

Who owns VANNTEKNIKK SØR AS?

BERNT IVAR GILJE ANDERSEN is the largest registered owner, with 60.0%.

What is the revenue of VANNTEKNIKK SØR AS?

VANNTEKNIKK SØR AS had revenue of NOK 4.3m in 2024.

Who is the general manager of VANNTEKNIKK SØR AS?

Bernt Ivar Gilje Andersen is registered as general manager of VANNTEKNIKK SØR AS.

Where is VANNTEKNIKK SØR AS based?

VANNTEKNIKK SØR AS has its business address in Grimstad.

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.