BIZTRAC BETA
Uoppgitt

VIA FORTUNA AS

Org. no. 935459427 Limited company (AS) Porsanger Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 841,000
Incorporated 2025
Share capital NOK 852,000

Signals

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

VIA FORTUNA AS is registered as a limited company in Porsanger, Finnmark with organisation number 935459427. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 852,000, divided into 793 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 841,000
Est. value
NOK 988,000

Financial health · 2025

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

Who owns VIA FORTUNA AS?

ANDERS ANDERSEN
VIA FORTUNA AS
NOK 0 rev. · NOK −5,000 profit

VIA FORTUNA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIA FORTUNA AS own?

VIA FORTUNA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VIA FORTUNA AS

Who owns VIA FORTUNA AS?

ANDERS ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of VIA FORTUNA AS?

VIA FORTUNA AS had revenue of NOK 0 in 2025.

Where is VIA FORTUNA AS based?

VIA FORTUNA AS has its business address in Lakselv.

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.