biztrac. BETA
COMPANY REGISTER PROFILE
916700490 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Water collection, treatment and supply

ULFENG VANN OG AVLØPSLAG SA

Org. no. 916700490 Co-operation (SA) Fredrikstad Incorporated 2016 Active
Ownership graph ↗
Revenue 2023 NOK 31,000
Operating profit NOK 8,000
Equity NOK 8,000
Incorporated 2016

ULFENG VANN OG AVLØPSLAG SA is registered as a co-operation in Fredrikstad, Østfold with organisation number 916700490. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2016. The company's stated purpose is: “Etablere, anlegge, eie, vedlikeholde og drifte et vann og avløpslag for medlemmene bosatt ved Ulfeng i Fredrikstad kommune.”. The most recent filed accounts, for the 2023 financial year, show NOK 31,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2023

Revenue
NOK 31,000
Operating profit
NOK 8,000
Equity
NOK 8,000
Est. value
NOK 26,000

Financial health · 2023

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
48.7%
Weak
Equity as a share of total capital

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

Who owns ULFENG VANN OG AVLØPSLAG SA?

No shareholders are registered for ULFENG VANN OG AVLØPSLAG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ULFENG VANN OG AVLØPSLAG SA

What is the revenue of ULFENG VANN OG AVLØPSLAG SA?

ULFENG VANN OG AVLØPSLAG SA had revenue of NOK 31,000 in 2023.

Who is the general manager of ULFENG VANN OG AVLØPSLAG SA?

Øystein Ulfeng Paulsen is registered as general manager of ULFENG VANN OG AVLØPSLAG SA.

Where is ULFENG VANN OG AVLØPSLAG SA based?

ULFENG VANN OG AVLØPSLAG SA has its business address in Gamle Fredrikstad.

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

Report a problem

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