BIZTRAC BETA
Web search portal activities

TALKLET AS

Org. no. 936677177 Limited company (AS) Malvik Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −40,000
Equity NOK 60,000
Incorporated 2025
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−40k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-18.

TALKLET AS is registered as a limited company in Malvik, Trøndelag with organisation number 936677177. The business is classified under web search portal activities (NACE 63.910). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Utvikling, drift og salg av programvare og digitale kommunikasjons- og læringstjenester, samt virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −40,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −40,000
Equity
NOK 60,000
Est. value
NOK 110,000

Financial health · 2025

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.4%
Weak
Equity as a share of total capital

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

Who owns TALKLET AS?

RUSTEN INVEST AS
TALKLET AS
NOK 0 rev. · NOK −40,000 profit

TALKLET AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TALKLET AS er morselskap for 1 datterselskap:

Frequently asked questions about TALKLET AS

Who owns TALKLET AS?

RUSTEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of TALKLET AS?

TALKLET AS had revenue of NOK 0 in 2025.

Where is TALKLET AS based?

TALKLET AS has its business address in Hommelvik.

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.