BIZTRAC BETA
Computer consultancy and computer facilities management activities

DIGILI AS

Org. no. 925927287 Limited company (AS) Hamar Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 101,000
Equity NOK 157,000
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-02-19 Adresseendring registrert 2026-02-19.

DIGILI AS is registered as a limited company in Hamar, Innlandet with organisation number 925927287. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Tilby konsulenttjenester innen programvareutvikling, programvarearkitektur og rådgivning. Drift av programvare-tjenester (SaaS, Software as a Service). Utvikling og vedlikehold av programvare.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 101,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 101,000
Equity
NOK 157,000
Est. value
NOK 664,000

Financial health · 2025

Liquidity
1.87
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
46.4%
Very good
Equity as a share of total capital

Who owns DIGILI AS?

ULF LILLEENGEN
DIGILI AS
NOK 1.3m rev. · NOK 101,000 profit

DIGILI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIGILI AS

Who owns DIGILI AS?

ULF LILLEENGEN is the largest registered owner, with 100.0%.

What is the revenue of DIGILI AS?

DIGILI AS had revenue of NOK 1.3m in 2025.

Who is the general manager of DIGILI AS?

Ulf Lilleengen is registered as general manager of DIGILI AS.

Where is DIGILI AS based?

DIGILI AS has its business address in Hamar.

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.