BIZTRAC BETA
Other activities of other membership organisations

MIDTVEGEN 615 AS

Org. no. 912681963 Limited company (AS) Gloppen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 50,000
Operating profit NOK 795
Equity NOK 118,000
Incorporated 2013
Share capital NOK 180,000

MIDTVEGEN 615 AS is registered as a limited company in Gloppen, Vestland with organisation number 912681963. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 2013. Registered share capital is NOK 180,000, divided into 450 shares. The company's stated purpose is: “Arbeide for utbygging og standardheving av fylkesveg 615 i Sogn og Fjordane fylke. Selskapet kan samarbeide med andre vegselskap for å delta i ein større samferdslepakke. Selskapet sitt overskot/underskot skal disponerast etter aksjelov og vedtekter. Det skal ikkje betalast utbytte til aksjonærane. Aksjane kan omsetjast fritt.”. The most recent filed accounts, for the 2024 financial year, show NOK 50,000 in revenue and NOK 795 in operating profit.

Key figures · 2024

Revenue
NOK 50,000
Operating profit
NOK 795
Equity
NOK 118,000
Est. value
NOK 73,000

Financial health · 2024

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

Who owns MIDTVEGEN 615 AS?

GLOPPEN KOMMUNE
MIDTVEGEN 615 AS
NOK 50,000 rev. · NOK 795 profit

MIDTVEGEN 615 AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about MIDTVEGEN 615 AS

Who owns MIDTVEGEN 615 AS?

GLOPPEN KOMMUNE is the largest registered owner, with 22.2%.

What is the revenue of MIDTVEGEN 615 AS?

MIDTVEGEN 615 AS had revenue of NOK 50,000 in 2024.

Where is MIDTVEGEN 615 AS based?

MIDTVEGEN 615 AS has its business address in Hyen.

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.