BIZTRAC BETA
Computer programming activities

DIGIWELLDATA AS

Org. no. 929619951 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −73,000
Equity NOK 163,000
Incorporated 2022
Share capital NOK 37,000

Signals

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

DIGIWELLDATA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929619951. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 37,000, divided into 36666 shares. The company's stated purpose is: “Utvikle og selge systemer, teknologi og software for planlegging og gjennomføring av bore- og brønnoperasjoner, samt delta i annen virksomhet med naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −73,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −73,000
Equity
NOK 163,000
Est. value
NOK 295,000

Financial health · 2024

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
71.3%
Very good
Equity as a share of total capital

Who owns DIGIWELLDATA AS?

BEHZAD ELAHIFAR
DIGIWELLDATA AS
NOK 0 rev. · NOK −73,000 profit

DIGIWELLDATA AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about DIGIWELLDATA AS

Who owns DIGIWELLDATA AS?

BEHZAD ELAHIFAR is the largest registered owner, with 40.9%.

What is the revenue of DIGIWELLDATA AS?

DIGIWELLDATA AS had revenue of NOK 0 in 2025.

Who is the general manager of DIGIWELLDATA AS?

Behzad Elahifar is registered as general manager of DIGIWELLDATA AS.

Where is DIGIWELLDATA AS based?

DIGIWELLDATA AS has its business address in Tiller.

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.