BIZTRAC BETA
Sports activities n.e.c.

FLYGIND GÅRD AS

Org. no. 818536372 Limited company (AS) Kongsvinger Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK −450,000
Equity NOK −5.2m
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−5,2 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−450k kr).

FLYGIND GÅRD AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 818536372. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drifte gård og hestestall. Eie hester, eiendom, aksjer, aksjefond og andre verdipapirer. Selskapet kan ved aksjeinnskudd, lån, garantistillelse eller på annen måte delta i annen næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK −450,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK −450,000
Equity
NOK −5.2m

Financial health · 2024

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

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

Who owns FLYGIND GÅRD AS?

FREDRIK HOLTH
FLYGIND GÅRD AS
NOK 1.8m rev. · NOK −450,000 profit

FLYGIND GÅRD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLYGIND GÅRD AS

Who owns FLYGIND GÅRD AS?

FREDRIK HOLTH is the largest registered owner, with 50.0%.

What is the revenue of FLYGIND GÅRD AS?

FLYGIND GÅRD AS had revenue of NOK 1.8m in 2024.

Where is FLYGIND GÅRD AS based?

FLYGIND GÅRD AS has its business address in Granli.

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.