biztrac. BETA
COMPANY REGISTER PROFILE
981693302 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

DEADLINE2ONLINE AS

Org. no. 981693302 Limited company (AS) Sandnes Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 56.0m
Operating profit NOK 12.7m
Equity NOK 73.9m
Incorporated 2000
Employees 7
Share capital NOK 600,000

DEADLINE2ONLINE AS is registered as a limited company in Sandnes, Rogaland with organisation number 981693302. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2000 and has 7 registered employees. Registered share capital is NOK 600,000, divided into 100002 shares. The company's stated purpose is: “Databehandlingstjenester, salg og utvikling av dataprogram, deltagelse i andre selskaper, og alt som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 56.0m in revenue and NOK 12.7m in operating profit.

Key figures · 2025

Revenue
NOK 56.0m
▲ +9 %
Operating profit
NOK 12.7m
▲ +20 %
Equity
NOK 73.9m
▲ +11 %
Est. value
NOK 114.1m

Financial health · 2025

Liquidity
12.89
Very good
Current assets ÷ current liabilities
Profitability
21.2%
Very good
Return on total assets
Solidity
92.5%
Very good
Equity as a share of total capital

Who owns DEADLINE2ONLINE AS?

DEADLINE2ONLINE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does DEADLINE2ONLINE AS own?

DEADLINE2ONLINE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DEADLINE2ONLINE AS

Who owns DEADLINE2ONLINE AS?

Young Ngoc Nguyen is the largest registered owner, with 42.4%.

What is the revenue of DEADLINE2ONLINE AS?

DEADLINE2ONLINE AS had revenue of NOK 56.0m in 2025.

Where is DEADLINE2ONLINE AS based?

DEADLINE2ONLINE AS has its business address in Sandnes.

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

Report a problem

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