BIZTRAC BETA
Buying and selling of own real estate

FYKSEN AS

Org. no. 922184143 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 1.4m
Incorporated 2019
Share capital NOK 115,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

FYKSEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922184143. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 115,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper, kjøp og salg av eiendommer og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 1.4m
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns FYKSEN AS?

OLE FYKSEN
FYKSEN AS
NOK 0 rev. · NOK −18,000 profit

FYKSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FYKSEN AS own?

FYKSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FYKSEN AS

Who owns FYKSEN AS?

OLE FYKSEN is the largest registered owner, with 100.0%.

What is the revenue of FYKSEN AS?

FYKSEN AS had revenue of NOK 0 in 2025.

Where is FYKSEN AS based?

FYKSEN 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.