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

FLØRENESVANN AS

Org. no. 957863949 Limited company (AS) Birkenes Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 121,000
Operating profit NOK 6,000
Equity NOK 185,000
Incorporated 1990
Share capital NOK 100,000

FLØRENESVANN AS is registered as a limited company in Birkenes, Agder with organisation number 957863949. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive vannverk/vannledning, samt alt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 121,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 121,000
▲ +56 %
Operating profit
NOK 6,000
▲ +183 %
Equity
NOK 185,000
▲ +4 %
Est. value
NOK 143,000

Financial health · 2025

Liquidity
8.43
Very good
Current assets ÷ current liabilities
Profitability
4.9%
Weak
Return on total assets
Solidity
88.1%
Very good
Equity as a share of total capital

Who owns FLØRENESVANN AS?

FLØRENESVANN AS
NOK 121,000 rev. · NOK 6,000 profit

FLØRENESVANN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLØRENESVANN AS

Who owns FLØRENESVANN AS?

JAN CHRISTIAN GRUNER SUNDT is the largest registered owner, with 100.0%.

What is the revenue of FLØRENESVANN AS?

FLØRENESVANN AS had revenue of NOK 121,000 in 2025.

Who is the general manager of FLØRENESVANN AS?

Jan Christian Gruner Sundt is registered as general manager of FLØRENESVANN AS.

Where is FLØRENESVANN AS based?

FLØRENESVANN AS has its business address in Birkeland.

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.