BIZTRAC BETA
COMPANY REGISTER PROFILE
915078680 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

DIN ERP HOLDING AS

Org. no. 915078680 Limited company (AS) Åfjord Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 4.6m
Incorporated 2015
Share capital NOK 4.0m

Signals

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

DIN ERP HOLDING AS is registered as a limited company in Åfjord, Trøndelag with organisation number 915078680. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 4.0m, divided into 4000000 shares. The company's stated purpose is: “Investeringer av aksjer og verdipapirer.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −417 %
Equity
NOK 4.6m
▼ −0 %
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
-36.56
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
102.7%
Very good
Equity as a share of total capital

Who owns DIN ERP HOLDING AS?

DIN ERP HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DIN ERP HOLDING AS

Who owns DIN ERP HOLDING AS?

TREFEM AS is the largest registered owner, with 33.3%.

Where is DIN ERP HOLDING AS based?

DIN ERP HOLDING AS has its business address in Åfjord.

Property

Business address c/o Roy Ugedal Stibergsvingen 10, 7170 Åfjord
Cadastral unit 5058-58/118/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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