BIZTRAC BETA
Business and other management consultancy activities

FYKEN EIERSKAP AS

Org. no. 915625045 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 76,000
Operating profit NOK 53,000
Equity NOK 15.5m
Incorporated 2015
Share capital NOK 100,000

FYKEN EIERSKAP AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915625045. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet, annen virksomhet som naturlig står i forbindelse med dette, herunder deltagelse i andre virksomheter, samt investering i aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 76,000 in revenue and NOK 53,000 in operating profit.

Key figures · 2024

Revenue
NOK 76,000
Operating profit
NOK 53,000
Equity
NOK 15.5m
Est. value
NOK 9.4m

Financial health · 2024

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

Who owns FYKEN EIERSKAP AS?

HANS OUST
FYKEN EIERSKAP AS
NOK 76,000 rev. · NOK 53,000 profit

FYKEN EIERSKAP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FYKEN EIERSKAP AS own?

FYKEN EIERSKAP AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about FYKEN EIERSKAP AS

Who owns FYKEN EIERSKAP AS?

HANS OUST is the largest registered owner, with 100.0%.

What is the revenue of FYKEN EIERSKAP AS?

FYKEN EIERSKAP AS had revenue of NOK 76,000 in 2024.

Where is FYKEN EIERSKAP AS based?

FYKEN EIERSKAP AS has its business address in Trondheim.

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.