biztrac. BETA
COMPANY REGISTER PROFILE
975339688 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of machine tools

DIGERNES AS

Org. no. 975339688 Limited company (AS) Time Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 95.6m
Operating profit NOK 9.6m
Equity NOK 6.7m
Incorporated 1995
Employees 13
Share capital NOK 475,000

DIGERNES AS is registered as a limited company in Time, Rogaland with organisation number 975339688. The business is classified under wholesale of machine tools (NACE 46.620). The company was incorporated in 1995 and has 13 registered employees. Registered share capital is NOK 475,000, divided into 4750 shares. The company's stated purpose is: “Handel, samt deltagelse i annen virksomhet og investering i eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 95.6m in revenue and NOK 9.6m in operating profit.

Key figures · 2025

Revenue
NOK 95.6m
▲ +10 %
Operating profit
NOK 9.6m
▼ −1 %
Equity
NOK 6.7m
▼ −26 %
Est. value
NOK 34.0m

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
30.0%
Very good
Return on total assets
Solidity
21.5%
Good
Equity as a share of total capital

Who owns DIGERNES AS?

DIGERNES AS
NOK 95.6m rev. · NOK 9.6m profit

DIGERNES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DIGERNES AS own?

DIGERNES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DIGERNES AS

Who owns DIGERNES AS?

EGE-GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of DIGERNES AS?

DIGERNES AS had revenue of NOK 95.6m in 2025.

Who is the general manager of DIGERNES AS?

Øystein Sande Johnsen is registered as general manager of DIGERNES AS.

Where is DIGERNES AS based?

DIGERNES AS has its business address in Bryne.

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.