BIZTRAC BETA
Rental and operating of own or leased real estate

FÅVANG FUTURUM AS

Org. no. 928132773 Limited company (AS) Lillehammer Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −47,000
Equity NOK −301,000
Incorporated 2021
Share capital NOK 102,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−301k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−47k kr).

FÅVANG FUTURUM AS is registered as a limited company in Lillehammer, Innlandet with organisation number 928132773. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 102,000, divided into 1020 shares. The company's stated purpose is: “Investeringer i fast eiendom og aksjer, drift og utleie av fast eiendom og annen virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −47,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −47,000
Equity
NOK −301,000

Financial health · 2025

Liquidity
0.53
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-9.8%
Weak
Equity as a share of total capital

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

Who owns FÅVANG FUTURUM AS?

ANDRÈ STENUMGÅRD HOLDING AS
FÅVANG FUTURUM AS
NOK 0 rev. · NOK −47,000 profit

FÅVANG FUTURUM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FÅVANG FUTURUM AS

Who owns FÅVANG FUTURUM AS?

ANDRÈ STENUMGÅRD HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of FÅVANG FUTURUM AS?

FÅVANG FUTURUM AS had revenue of NOK 0 in 2025.

Where is FÅVANG FUTURUM AS based?

FÅVANG FUTURUM AS has its business address in Lillehammer.

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.