BIZTRAC BETA
Water collection, treatment and supply

DRANGSVATN NORD AS

Org. no. 915207308 Limited company (AS) Nissedal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −100,000
Equity NOK 227,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−100k kr).

DRANGSVATN NORD AS is registered as a limited company in Nissedal, Telemark with organisation number 915207308. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Etablere og drifte et privat renseanlegg/vannverk med tilhørende ledningssystem for opptil 7 eiendommer i Drangsvatn Hyttegrend i Nissedal kommune.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −100,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −100,000
Equity
NOK 227,000
Est. value
NOK 241,000

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
88.3%
Very good
Equity as a share of total capital

Who owns DRANGSVATN NORD AS?

ANDERS TVEITAN
DRANGSVATN NORD AS
NOK 0 rev. · NOK −100,000 profit

DRANGSVATN NORD AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRANGSVATN NORD AS

Who owns DRANGSVATN NORD AS?

ANDERS TVEITAN is the largest registered owner, with 20.0%.

What is the revenue of DRANGSVATN NORD AS?

DRANGSVATN NORD AS had revenue of NOK 0 in 2025.

Who is the general manager of DRANGSVATN NORD AS?

Kjetil Nakken is registered as general manager of DRANGSVATN NORD AS.

Where is DRANGSVATN NORD AS based?

DRANGSVATN NORD AS has its business address in Åmli.

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.