BIZTRAC BETA
Computer programming activities

DIGGECARD SOLUTIONS AS

Org. no. 932863359 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 15.9m
Operating profit NOK 4.5m
Equity NOK 1.0m
Incorporated 2023
Employees 5
Share capital NOK 30,000

DIGGECARD SOLUTIONS AS is registered as a limited company in Bergen, Vestland with organisation number 932863359. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Utvikle og distribuere løsning for elektroniske gavekort, eie aksjer og andeler i andre selskaper med tilsvarende formål samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.9m in revenue and NOK 4.5m in operating profit.

Key figures · 2024

Revenue
NOK 15.9m
Operating profit
NOK 4.5m
Equity
NOK 1.0m
Est. value
NOK 19.9m

Financial health · 2024

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

Who owns DIGGECARD SOLUTIONS AS?

DIGGECARD AS
DIGGECARD SOLUTIONS AS
NOK 15.9m rev. · NOK 4.5m profit

DIGGECARD SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIGGECARD SOLUTIONS AS

Who owns DIGGECARD SOLUTIONS AS?

DIGGECARD AS is the largest registered owner, with 100.0%.

What is the revenue of DIGGECARD SOLUTIONS AS?

DIGGECARD SOLUTIONS AS had revenue of NOK 15.9m in 2024.

Who is the general manager of DIGGECARD SOLUTIONS AS?

Arvid Torset is registered as general manager of DIGGECARD SOLUTIONS AS.

Where is DIGGECARD SOLUTIONS AS based?

DIGGECARD SOLUTIONS AS has its business address in Bergen.

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.