BIZTRAC BETA
Rental and operating of own or leased real estate

FURRE FELLESFJØS AS

Org. no. 916283865 Limited company (AS) Overhalla Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 573,000
Equity NOK −2.0m
Incorporated 2015
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,0 mill kr).

FURRE FELLESFJØS AS is registered as a limited company in Overhalla, Trøndelag with organisation number 916283865. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Å erverve, bygge og forvalte fast eiendom med driftsbygninger for utleie til næringsvirksomhet, samt annen virksomhet som er naturlig knyttet til landbruket.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 573,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 573,000
Equity
NOK −2.0m
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
2.13
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-26.1%
Weak
Equity as a share of total capital

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

Who owns FURRE FELLESFJØS AS?

JOAKIM RØNNING
FURRE FELLESFJØS AS
NOK 1.2m rev. · NOK 573,000 profit

FURRE FELLESFJØS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FURRE FELLESFJØS AS

Who owns FURRE FELLESFJØS AS?

JOAKIM RØNNING is the largest registered owner, with 50.0%.

What is the revenue of FURRE FELLESFJØS AS?

FURRE FELLESFJØS AS had revenue of NOK 1.2m in 2024.

Where is FURRE FELLESFJØS AS based?

FURRE FELLESFJØS AS has its business address in Overhalla.

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.