BIZTRAC BETA
COMPANY REGISTER PROFILE
891876882 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Water collection, treatment and supply

UNDERBERGET VANNSELSKAP BA

Org. no. 891876882 Company with limited liability (BA) Flesberg Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 346,000
Operating profit NOK 12,000
Equity NOK 325,000
Incorporated 2007

UNDERBERGET VANNSELSKAP BA is registered as a company with limited liability in Flesberg, Buskerud with organisation number 891876882. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2007. The company's stated purpose is: “Investering, etablering, drift og utvikling av anlegg for vannforsyning og annen infrastruktrur for mot vederlag å tilby dette til hytteeierer og næringsvirksomheter på eiendommene Søndre Underberget Gård (gnr 14 bnr 2) og Nordre Underberget Gård (gnr 14 bnr 1 og 3) på Blefjell og det som hører sammen med slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 346,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 346,000
Operating profit
NOK 12,000
Equity
NOK 325,000
Est. value
NOK 236,000

Financial health · 2025

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

Who owns UNDERBERGET VANNSELSKAP BA?

No shareholders are registered for UNDERBERGET VANNSELSKAP BA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about UNDERBERGET VANNSELSKAP BA

What is the revenue of UNDERBERGET VANNSELSKAP BA?

UNDERBERGET VANNSELSKAP BA had revenue of NOK 346,000 in 2025.

Where is UNDERBERGET VANNSELSKAP BA based?

UNDERBERGET VANNSELSKAP BA has its business address in Lampeland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.