BIZTRAC BETA
Fund management activities

TRESS FONDS AS

Org. no. 920362214 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −1.4m
Equity NOK 2.7m
Incorporated 2018
Share capital NOK 2.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,4 mill kr).

TRESS FONDS AS is registered as a limited company in Oslo, Oslo with organisation number 920362214. The business is classified under fund management activities (NACE 66.300). The company was incorporated in 2018. Registered share capital is NOK 2.0m, divided into 100000 shares. The company's stated purpose is: “Forvalter av alternative investeringsfond, og annen virksomhet som står i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −1.4m in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −1.4m
Equity
NOK 2.7m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns TRESS FONDS AS?

TRESS EIENDOM HOLDING AS
TRESS FONDS AS
NOK 1.3m rev. · NOK −1.4m profit

TRESS FONDS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRESS FONDS AS own?

TRESS FONDS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRESS FONDS AS

Who owns TRESS FONDS AS?

TRESS EIENDOM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TRESS FONDS AS?

TRESS FONDS AS had revenue of NOK 1.3m in 2025.

Who is the general manager of TRESS FONDS AS?

Jarle Villumstad is registered as general manager of TRESS FONDS AS.

Where is TRESS FONDS AS based?

TRESS FONDS 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.