BIZTRAC BETA
Rental and operating of own or leased real estate

NAVESTA AS

Org. no. 913410769 Limited company (AS) Fredrikstad Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 129,000
Operating profit NOK −9.2m
Equity NOK 42.4m
Incorporated 2014
Share capital NOK 660,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9,2 mill kr).

NAVESTA AS is registered as a limited company in Fredrikstad, Østfold with organisation number 913410769. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 660,000, divided into 60000 shares. The company's stated purpose is: “Investere i og eie andeler i andre selskaper, fast eiendom og andre eiendeler, samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 129,000 in revenue and NOK −9.2m in operating profit.

Key figures · 2024

Revenue
NOK 129,000
Operating profit
NOK −9.2m
Equity
NOK 42.4m
Est. value
NOK 29.2m

Financial health · 2024

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

Who owns NAVESTA AS?

TRULS NAVESTAD
NAVESTA AS
NOK 129,000 rev. · NOK −9.2m profit

NAVESTA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NAVESTA AS own?

NAVESTA AS holds stakes in 6 companies:

See the full ownership structure →

Group structure

NAVESTA AS er morselskap for 1 datterselskap:

Frequently asked questions about NAVESTA AS

Who owns NAVESTA AS?

TRULS NAVESTAD is the largest registered owner, with 100.0%.

What is the revenue of NAVESTA AS?

NAVESTA AS had revenue of NOK 129,000 in 2024.

Where is NAVESTA AS based?

NAVESTA AS has its business address in Fredrikstad.

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.