BIZTRAC BETA
Other real estate activities on a fee or contract basis

PURE FUTURE AS

Org. no. 812288652 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −123,000
Equity NOK 4.8m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−123k kr).

PURE FUTURE AS is registered as a limited company in Oslo, Oslo with organisation number 812288652. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å eie og forvalte aksjer, verdipapirer, fast eiendom og andre formuesgjenstander, i tillegg foreta investering i virksomheter, samt finansiering.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −123,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −123,000
Equity
NOK 4.8m
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns PURE FUTURE AS?

ANNE METTE MUNCH-THORE
PURE FUTURE AS
NOK 0 rev. · NOK −123,000 profit

PURE FUTURE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PURE FUTURE AS own?

PURE FUTURE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about PURE FUTURE AS

Who owns PURE FUTURE AS?

ANNE METTE MUNCH-THORE is the largest registered owner, with 100.0%.

What is the revenue of PURE FUTURE AS?

PURE FUTURE AS had revenue of NOK 0 in 2024.

Where is PURE FUTURE AS based?

PURE FUTURE AS has its business address in Oslo.

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.