BIZTRAC BETA
Other specialised construction activities n.e.c.

FAGERHEIM INVEST AS

Org. no. 989074075 Limited company (AS) Vik Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 590,000
Equity NOK 924,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FAGERHEIM INVEST AS is registered as a limited company in Vik, Vestland with organisation number 989074075. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investera i aksjar og fast eigedom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 590,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 590,000
Equity
NOK 924,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns FAGERHEIM INVEST AS?

BJARTMAR TJØNN RINDE
FAGERHEIM INVEST AS
NOK 1.1m rev. · NOK 590,000 profit

FAGERHEIM INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FAGERHEIM INVEST AS own?

FAGERHEIM INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FAGERHEIM INVEST AS

Who owns FAGERHEIM INVEST AS?

BJARTMAR TJØNN RINDE is the largest registered owner, with 50.0%.

What is the revenue of FAGERHEIM INVEST AS?

FAGERHEIM INVEST AS had revenue of NOK 1.1m in 2024.

Where is FAGERHEIM INVEST AS based?

FAGERHEIM INVEST AS has its business address in Vik I Sogn.

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.