BIZTRAC BETA
Other captive investment companies

FÆRGESTAD INVEST AS

Org. no. 919710764 Limited company (AS) Rælingen Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −36,000
Equity NOK 24.7m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−36k kr).

FÆRGESTAD INVEST AS is registered as a limited company in Rælingen, Akershus with organisation number 919710764. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i aksjer, konsulenttjenester og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK −36,000
Equity
NOK 24.7m
Est. value
NOK 17.7m

Financial health · 2025

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

Who owns FÆRGESTAD INVEST AS?

MAGNUS TEIE FÆRGESTAD
FÆRGESTAD INVEST AS
· NOK −36,000 profit

FÆRGESTAD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FÆRGESTAD INVEST AS own?

FÆRGESTAD INVEST AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about FÆRGESTAD INVEST AS

Who owns FÆRGESTAD INVEST AS?

MAGNUS TEIE FÆRGESTAD is the largest registered owner, with 100.0%.

Who is the general manager of FÆRGESTAD INVEST AS?

Magnus Teie Færgestad is registered as general manager of FÆRGESTAD INVEST AS.

Where is FÆRGESTAD INVEST AS based?

FÆRGESTAD INVEST AS has its business address in Fjerdingby.

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.