BIZTRAC BETA
COMPANY REGISTER PROFILE
934967216 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Computer programming activities

TALKIT AS

Org. no. 934967216 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −397,000
Equity NOK 334,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−397k kr).

TALKIT AS is registered as a limited company in Oslo, Oslo with organisation number 934967216. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 4286 shares. The company's stated purpose is: “Utvikling, drift og markedsføring av et AI-basert system med mål om å effektivisere dokumentasjon i helsevesenet og andre relevante sektorer.”.

Former names: AISSIST AS

Key figures · 2025

Operating profit
NOK −397,000
Equity
NOK 334,000
Est. value
NOK 605,000

Financial health · 2025

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

Who owns TALKIT AS?

TALKIT AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about TALKIT AS

Who owns TALKIT AS?

SHAH VENTURES AS is the largest registered owner, with 16.1%.

Where is TALKIT AS based?

TALKIT AS has its business address in Oslo.

Property

Business address Erich Mogensøns vei 38, 0594 Oslo
Cadastral unit 301-88/307/0/0

66 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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