BIZTRAC BETA
Other real estate activities on a fee or contract basis

TREKON AS

Org. no. 920884830 Limited company (AS) Lillehammer Incorporated 1975 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 1.5m
Incorporated 1975
Share capital NOK 501,000

Signals

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

TREKON AS is registered as a limited company in Lillehammer, Innlandet with organisation number 920884830. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1975. Registered share capital is NOK 501,000. The company's stated purpose is: “Drive forretningsvirksomhet av enhver art herunder være deltaker i andre selskaper med slikt formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 1.5m
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns TREKON AS?

JOHAN SKIKSTEIN SOLLI
TREKON AS
NOK 0 rev. · NOK −28,000 profit

TREKON AS has 10 registered shareholders:

All shareholders and roles →

Which companies does TREKON AS own?

TREKON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TREKON AS

Who owns TREKON AS?

JOHAN SKIKSTEIN SOLLI is the largest registered owner, with 15.4%.

What is the revenue of TREKON AS?

TREKON AS had revenue of NOK 0 in 2025.

Who is the general manager of TREKON AS?

Johan Skikstein Solli is registered as general manager of TREKON AS.

Where is TREKON AS based?

TREKON AS has its business address in Lillehammer.

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.