BIZTRAC BETA
Retail sale of sports equipment

FJELLTIND AS

Org. no. 922871159 Limited company (AS) Øygarden Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK 860,000
Equity NOK 1.5m
Incorporated 2019
Employees 5
Share capital NOK 30,000

FJELLTIND AS is registered as a limited company in Øygarden, Vestland with organisation number 922871159. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Internetthandel med varer, agenturvirksomhet, samt hva som hermed står i forbindelse. Fremstilling, import, salg og service av teknisk utstyr samt merkesystemer og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK 860,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK 860,000
Equity
NOK 1.5m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns FJELLTIND AS?

GIHL HOLDING AS
FJELLTIND AS
NOK 7.4m rev. · NOK 860,000 profit

FJELLTIND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJELLTIND AS

Who owns FJELLTIND AS?

GIHL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FJELLTIND AS?

FJELLTIND AS had revenue of NOK 7.4m in 2024.

Who is the general manager of FJELLTIND AS?

Irene Gihl Lindberg is registered as general manager of FJELLTIND AS.

Where is FJELLTIND AS based?

FJELLTIND AS has its business address in Steinsland.

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.