BIZTRAC BETA
COMPANY REGISTER PROFILE
934400054 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Sewerage

MÅNVEGEN AVLØP SA

Org. no. 934400054 Co-operation (SA) Asker Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 130,000
Incorporated 2024

Signals

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

MÅNVEGEN AVLØP SA is registered as a co-operation in Asker, Akershus with organisation number 934400054. The business is classified under sewerage (NACE 37.000). The company was incorporated in 2024. The company's stated purpose is: “Etablere felles avløpsanlegg for eiendommene 65/18, 65/19, 65/20 og 65/3 ved Månvegen i Nore og Uvdal kommune. Formålet er å få til en beste mulig løsning i forhold til investering, drift og for å kunne ivareta miljøforhold på en god måte.”.

Key figures · 2025

Operating profit
NOK −14,000
Equity
NOK 130,000
Est. value
NOK 138,000

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.1%
Satisfactory
Equity as a share of total capital

Who owns MÅNVEGEN AVLØP SA?

No shareholders are registered for MÅNVEGEN AVLØP SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MÅNVEGEN AVLØP SA

Where is MÅNVEGEN AVLØP SA based?

MÅNVEGEN AVLØP SA has its business address in Asker.

Property

Business address Gullhellaveien 13B, 1386 Asker
Cadastral unit 3203-61/647/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.