biztrac. BETA
COMPANY REGISTER PROFILE
986279423 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Site preparation

INTERACTIVE AS

Org. no. 986279423 Limited company (AS) Drammen Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 436,000
Operating profit NOK −142,000
Equity NOK −2.7m
Incorporated 2003
Share capital NOK 469,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,7 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−142k kr).

INTERACTIVE AS is registered as a limited company in Drammen, Buskerud with organisation number 986279423. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2003. Registered share capital is NOK 469,000, divided into 117125 shares. The company's stated purpose is: “Utføre mindre entreprenøroppdrag. Kjøp og salg av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 436,000 in revenue and NOK −142,000 in operating profit.

Former names: INTERACTIVE SMS AS

Key figures · 2025

Revenue
NOK 436,000
▼ −58 %
Operating profit
NOK −142,000
▲ +89 %
Equity
NOK −2.7m
▼ −8 %

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
-101.4%
Not satisfactory
Return on total assets
Solidity
-1965.0%
Weak
Equity as a share of total capital

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

Who owns INTERACTIVE AS?

INTERACTIVE AS
NOK 436,000 rev. · NOK −142,000 profit

INTERACTIVE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about INTERACTIVE AS

Who owns INTERACTIVE AS?

Jan Gurrik is the largest registered owner, with 40.0%.

What is the revenue of INTERACTIVE AS?

INTERACTIVE AS had revenue of NOK 436,000 in 2025.

Where is INTERACTIVE AS based?

INTERACTIVE AS has its business address in Drammen.

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.