BIZTRAC BETA
Business and other management consultancy activities

FUTURO MANAGEMENT AS

Org. no. 990859809 Limited company (AS) Rælingen Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 8.0m
Operating profit NOK 4.0m
Equity NOK 84,000
Incorporated 2007
Share capital NOK 30,000

FUTURO MANAGEMENT AS is registered as a limited company in Rælingen, Akershus with organisation number 990859809. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2007. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rådgivning og konsulentvirksomhet, samt deltagelse og investeringer i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.0m in revenue and NOK 4.0m in operating profit.

Key figures · 2025

Revenue
NOK 8.0m
Operating profit
NOK 4.0m
Equity
NOK 84,000
Est. value
NOK 12.0m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.6%
Weak
Equity as a share of total capital

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

Who owns FUTURO MANAGEMENT AS?

PER MAGNE BJØRNSLETT
FUTURO MANAGEMENT AS
NOK 8.0m rev. · NOK 4.0m profit

FUTURO MANAGEMENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FUTURO MANAGEMENT AS

Who owns FUTURO MANAGEMENT AS?

PER MAGNE BJØRNSLETT is the largest registered owner, with 100.0%.

What is the revenue of FUTURO MANAGEMENT AS?

FUTURO MANAGEMENT AS had revenue of NOK 8.0m in 2025.

Who is the general manager of FUTURO MANAGEMENT AS?

Per Magne Bjørnslett is registered as general manager of FUTURO MANAGEMENT AS.

Where is FUTURO MANAGEMENT AS based?

FUTURO MANAGEMENT AS has its business address in Løvenstad.

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.