BIZTRAC BETA
Web search portal activities

INTERSIKT AS

Org. no. 934012763 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 25,000
Operating profit NOK −9,000
Equity NOK 22,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

INTERSIKT AS is registered as a limited company in Oslo, Oslo with organisation number 934012763. The business is classified under web search portal activities (NACE 63.910). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen drift av web-portaler - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 25,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 25,000
Operating profit
NOK −9,000
Equity
NOK 22,000
Est. value
NOK 52,000

Financial health · 2024

Liquidity
2.32
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.7%
Weak
Equity as a share of total capital

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

Who owns INTERSIKT AS?

AMRUTHAA KISHORE
INTERSIKT AS
NOK 25,000 rev. · NOK −9,000 profit

INTERSIKT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about INTERSIKT AS

Who owns INTERSIKT AS?

AMRUTHAA KISHORE is the largest registered owner, with 52.0%.

What is the revenue of INTERSIKT AS?

INTERSIKT AS had revenue of NOK 25,000 in 2024.

Who is the general manager of INTERSIKT AS?

Amruthaa Kishore is registered as general manager of INTERSIKT AS.

Where is INTERSIKT AS based?

INTERSIKT AS has its business address in Oslo.

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.