BIZTRAC BETA
Research and experimental development on natural sciences and engineering

FUTURELAB.NO AS

Org. no. 921826222 Limited company (AS) Moss Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11,000
Equity NOK −38,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−38k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).

FUTURELAB.NO AS is registered as a limited company in Moss, Østfold with organisation number 921826222. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bidra til forskning, kartlegging og formidling av utfordringer knyttet til forekomsten av mikroplast i havet, både nasjonalt og internasjonalt.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK −38,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns FUTURELAB.NO AS?

SALT LIFE AS
FUTURELAB.NO AS
NOK 0 rev. · NOK −11,000 profit

FUTURELAB.NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FUTURELAB.NO AS

Who owns FUTURELAB.NO AS?

SALT LIFE AS is the largest registered owner, with 100.0%.

What is the revenue of FUTURELAB.NO AS?

FUTURELAB.NO AS had revenue of NOK 0 in 2024.

Where is FUTURELAB.NO AS based?

FUTURELAB.NO AS has its business address in Moss.

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.