biztrac. BETA
COMPANY REGISTER PROFILE
895921092 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of mining, construction and civil engineering machinery

BERGTEKNIKK AS

Org. no. 895921092 Limited company (AS) Lindesnes Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 200,000
Equity NOK 2.1m
Incorporated 2010
Share capital NOK 740,000

BERGTEKNIKK AS is registered as a limited company in Lindesnes, Agder with organisation number 895921092. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2010. Registered share capital is NOK 740,000, divided into 740 shares. The company's stated purpose is: “Salg og konsulenttjenester innen bygg og anlegg og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 200,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
▼ −24 %
Operating profit
NOK 200,000
▼ −8 %
Equity
NOK 2.1m
▲ +93 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
1.66
Good
Current assets ÷ current liabilities
Profitability
8.0%
Satisfactory
Return on total assets
Solidity
73.7%
Very good
Equity as a share of total capital

Who owns BERGTEKNIKK AS?

FYKSEN INVEST AS NO
BERGTEKNIKK AS
NOK 3.2m rev. · NOK 200,000 profit

BERGTEKNIKK AS has 1 registered shareholder:

  • FYKSEN INVEST AS 100.0%
All shareholders and roles →

Frequently asked questions about BERGTEKNIKK AS

Who owns BERGTEKNIKK AS?

FYKSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BERGTEKNIKK AS?

BERGTEKNIKK AS had revenue of NOK 3.2m in 2025.

Who is the general manager of BERGTEKNIKK AS?

Ståle Fyksen is registered as general manager of BERGTEKNIKK AS.

Where is BERGTEKNIKK AS based?

BERGTEKNIKK AS has its business address in Øyslebø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.