BIZTRAC BETA
Motion picture, video and television programme production activities

TIKA 1 AS

Org. no. 984215533 Limited company (AS) Stavanger Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 6,000
Operating profit NOK 2,000
Equity NOK 76,000
Incorporated 2002
Share capital NOK 315,000

TIKA 1 AS is registered as a limited company in Stavanger, Rogaland with organisation number 984215533. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2002. Registered share capital is NOK 315,000, divided into 315 shares. The company's stated purpose is: “Helse senter, helsekost fremstilling/import og salg, kursvirksomhet, behandlinger innen naturterapi/medisin, SPA - kursenter, helsefarm/hotell - helsereiser, TV - program, internett salg, konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 6,000
Operating profit
NOK 2,000
Equity
NOK 76,000
Est. value
NOK 47,000

Financial health · 2025

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

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

Who owns TIKA 1 AS?

TONE ANITA FINNESAND
TIKA 1 AS
NOK 6,000 rev. · NOK 2,000 profit

TIKA 1 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIKA 1 AS

Who owns TIKA 1 AS?

TONE ANITA FINNESAND is the largest registered owner, with 50.2%.

What is the revenue of TIKA 1 AS?

TIKA 1 AS had revenue of NOK 6,000 in 2025.

Who is the general manager of TIKA 1 AS?

Tone Anita Finnesand is registered as general manager of TIKA 1 AS.

Where is TIKA 1 AS based?

TIKA 1 AS has its business address in Rennesøy.

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.