BIZTRAC BETA
Business and other management consultancy activities

FUTURE FUNDING AS

Org. no. 925355135 Limited company (AS) Lørenskog Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 1.5m
Incorporated 2020
Share capital NOK 30,000

Signals

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

FUTURE FUNDING AS is registered as a limited company in Lørenskog, Akershus with organisation number 925355135. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, eiendom og andre verdipapirer. Rådgivning innen økonomi, økonomistyring og alt som hører til dette faget.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 1.5m
Est. value
NOK 8.3m

Financial health · 2025

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

Who owns FUTURE FUNDING AS?

WASIM ULLAH
FUTURE FUNDING AS
NOK 0 rev. · NOK −15,000 profit

FUTURE FUNDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FUTURE FUNDING AS own?

FUTURE FUNDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FUTURE FUNDING AS

Who owns FUTURE FUNDING AS?

WASIM ULLAH is the largest registered owner, with 100.0%.

What is the revenue of FUTURE FUNDING AS?

FUTURE FUNDING AS had revenue of NOK 0 in 2025.

Where is FUTURE FUNDING AS based?

FUTURE FUNDING AS has its business address in Lørenskog.

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.