BIZTRAC BETA
Activities of advertising agencies

LOKI TALK AS

Org. no. 933909271 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 147,000
Operating profit NOK 998
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

LOKI TALK AS is registered as a limited company in Oslo, Oslo with organisation number 933909271. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby tjenester innen markedsføring og reklame på internett, inkludert, men ikke begrenset til, markedsføringsstrategi, annonsering, merkevarebygging, utvikling av internett-løsninger, digital markedsføring og andre relaterte tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 147,000 in revenue and NOK 998 in operating profit.

Key figures · 2024

Revenue
NOK 147,000
Operating profit
NOK 998
Equity
NOK 24,000
Est. value
NOK 22,000

Financial health · 2024

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

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

Who owns LOKI TALK AS?

ESPEN KRISTOFFERSTUEN
LOKI TALK AS
NOK 147,000 rev. · NOK 998 profit

LOKI TALK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOKI TALK AS

Who owns LOKI TALK AS?

ESPEN KRISTOFFERSTUEN is the largest registered owner, with 33.3%.

What is the revenue of LOKI TALK AS?

LOKI TALK AS had revenue of NOK 147,000 in 2024.

Who is the general manager of LOKI TALK AS?

Kurt Laukvik is registered as general manager of LOKI TALK AS.

Where is LOKI TALK AS based?

LOKI TALK 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.