BIZTRAC BETA
Uoppgitt

FUTR HOLDING AS

Org. no. 921251246 Limited company (AS) Ullensaker Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 300,000
Operating profit NOK 215,000
Equity NOK −114,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−114k kr).

FUTR HOLDING AS is registered as a limited company in Ullensaker, Akershus with organisation number 921251246. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i egne selskaper, investeringer i verdipapirer og fond, prosjekter i egen regi, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 300,000 in revenue and NOK 215,000 in operating profit.

Key figures · 2024

Revenue
NOK 300,000
Operating profit
NOK 215,000
Equity
NOK −114,000
Est. value
NOK 1.1m

Financial health · 2024

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

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

Who owns FUTR HOLDING AS?

REMY SKOGSTRAND
FUTR HOLDING AS
NOK 300,000 rev. · NOK 215,000 profit

FUTR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FUTR HOLDING AS

Who owns FUTR HOLDING AS?

REMY SKOGSTRAND is the largest registered owner, with 100.0%.

What is the revenue of FUTR HOLDING AS?

FUTR HOLDING AS had revenue of NOK 300,000 in 2024.

Who is the general manager of FUTR HOLDING AS?

Remy Skogstrand is registered as general manager of FUTR HOLDING AS.

Where is FUTR HOLDING AS based?

FUTR HOLDING AS has its business address in Mogreina.

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.