BIZTRAC BETA
Technical testing and analysis

MATERIAL TESTING AS

Org. no. 926848194 Limited company (AS) Sandnes Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK 642,000
Equity NOK 1.3m
Incorporated 2021
Employees 8
Share capital NOK 3.2m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MATERIAL TESTING AS is registered as a limited company in Sandnes, Rogaland with organisation number 926848194. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2021 and has 8 registered employees. Registered share capital is NOK 3.2m, divided into 3200000 shares. The company's stated purpose is: “Investering i andre selskap og maskiner.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 642,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
Operating profit
NOK 642,000
Equity
NOK 1.3m
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
0.55
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.4%
Good
Equity as a share of total capital

Who owns MATERIAL TESTING AS?

HESKESTAD HOLDING AS
MATERIAL TESTING AS
NOK 9.4m rev. · NOK 642,000 profit

MATERIAL TESTING AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about MATERIAL TESTING AS

Who owns MATERIAL TESTING AS?

HESKESTAD HOLDING AS is the largest registered owner, with 56.2%.

What is the revenue of MATERIAL TESTING AS?

MATERIAL TESTING AS had revenue of NOK 9.4m in 2025.

Who is the general manager of MATERIAL TESTING AS?

Idar Tobias Heskestad is registered as general manager of MATERIAL TESTING AS.

Where is MATERIAL TESTING AS based?

MATERIAL TESTING AS has its business address in Forsand.

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.