biztrac. BETA
COMPANY REGISTER PROFILE
970956131 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Operation of gravel and sand pits and mining of clay and kaolin

EIDE SANDTAK AS

Org. no. 970956131 Limited company (AS) Gloppen Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 14.2m
Operating profit NOK 4.1m
Equity NOK 14.2m
Incorporated 1994
Share capital NOK 400,000

EIDE SANDTAK AS is registered as a limited company in Gloppen, Vestland with organisation number 970956131. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 1994. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Drive sandtak med sal av dertilhøyrande varer og tenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.2m in revenue and NOK 4.1m in operating profit.

Former names: R JAKOBSEN MASKIN AS

Key figures · 2025

Revenue
NOK 14.2m
▼ −1 %
Operating profit
NOK 4.1m
▲ +45 %
Equity
NOK 14.2m
▲ +29 %
Est. value
NOK 18.1m

Financial health · 2025

Liquidity
4.28
Very good
Current assets ÷ current liabilities
Profitability
23.5%
Very good
Return on total assets
Solidity
76.7%
Very good
Equity as a share of total capital

Who owns EIDE SANDTAK AS?

EIDE SANDTAK AS
NOK 14.2m rev. · NOK 4.1m profit

EIDE SANDTAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIDE SANDTAK AS

Who owns EIDE SANDTAK AS?

OLAV HJELMESET AS is the largest registered owner, with 100.0%.

What is the revenue of EIDE SANDTAK AS?

EIDE SANDTAK AS had revenue of NOK 14.2m in 2025.

Who is the general manager of EIDE SANDTAK AS?

Stig Seime is registered as general manager of EIDE SANDTAK AS.

Where is EIDE SANDTAK AS based?

EIDE SANDTAK AS has its business address in Sandane.

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.