BIZTRAC BETA
Production of meat and poultry meat products

FJELLVILT AS

Org. no. 974457237 Limited company (AS) Røros Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −679,000
Equity NOK −444,000
Incorporated 1995
Share capital NOK 450,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−444k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−679k kr).

FJELLVILT AS is registered as a limited company in Røros, Trøndelag with organisation number 974457237. The business is classified under production of meat and poultry meat products (NACE 10.130). The company was incorporated in 1995. Registered share capital is NOK 450,000. The company's stated purpose is: “Foredling av reinskjøtt, annet kjøtt & fisk og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −679,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −679,000
Equity
NOK −444,000

Financial health · 2024

Liquidity
0.37
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-124.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FJELLVILT AS?

Nils Tonny Bransfjell
FJELLVILT AS
NOK 0 rev. · NOK −679,000 profit

FJELLVILT AS has 7 registered shareholders:

All shareholders and roles →

Which companies does FJELLVILT AS own?

FJELLVILT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FJELLVILT AS

Who owns FJELLVILT AS?

Nils Tonny Bransfjell is the largest registered owner, with 49.8%.

What is the revenue of FJELLVILT AS?

FJELLVILT AS had revenue of NOK 0 in 2024.

Where is FJELLVILT AS based?

FJELLVILT AS has its business address in Brekkebygd.

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.