BIZTRAC BETA
Computer programming activities

TID & KONTROLL AS

Org. no. 923773533 Limited company (AS) Moss Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 1.7m
Equity NOK −268,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−268k kr).

TID & KONTROLL AS is registered as a limited company in Moss, Østfold with organisation number 923773533. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg og utvikling av mobile-applikasjoner, annen software og hardware, samt alt som herunder hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 1.7m
Equity
NOK −268,000
Est. value
NOK 7.4m

Financial health · 2025

Liquidity
0.66
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-14.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TID & KONTROLL AS?

DKM GROUP AS
TID & KONTROLL AS
NOK 2.0m rev. · NOK 1.7m profit

TID & KONTROLL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TID & KONTROLL AS

Who owns TID & KONTROLL AS?

DKM GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of TID & KONTROLL AS?

TID & KONTROLL AS had revenue of NOK 2.0m in 2025.

Who is the general manager of TID & KONTROLL AS?

Sokrates Kalenderidis is registered as general manager of TID & KONTROLL AS.

Where is TID & KONTROLL AS based?

TID & KONTROLL AS has its business address in Moss.

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.