BIZTRAC BETA
Wholesale of other machinery and equipment

FUGLVIKA HOLDING AS

Org. no. 995557592 Limited company (AS) Steinkjer Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK 664,000
Incorporated 2010
Share capital NOK 100,000

Signals

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

FUGLVIKA HOLDING AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 995557592. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper og ellers det som faller naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 664,000
Est. value
NOK 830,000

Financial health · 2024

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

Who owns FUGLVIKA HOLDING AS?

KJELL BJØRNAR WENNEVIK
FUGLVIKA HOLDING AS
NOK 0 rev. · NOK −24,000 profit

FUGLVIKA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FUGLVIKA HOLDING AS own?

FUGLVIKA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FUGLVIKA HOLDING AS

Who owns FUGLVIKA HOLDING AS?

KJELL BJØRNAR WENNEVIK is the largest registered owner, with 100.0%.

What is the revenue of FUGLVIKA HOLDING AS?

FUGLVIKA HOLDING AS had revenue of NOK 0 in 2024.

Where is FUGLVIKA HOLDING AS based?

FUGLVIKA HOLDING AS has its business address in Steinkjer.

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.