BIZTRAC BETA
Visual arts creation activities

TINKER STUDIO AS

Org. no. 917633002 Limited company (AS) Drammen Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 256,000
Operating profit NOK −179,000
Equity NOK −13,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−13k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−179k kr).

TINKER STUDIO AS is registered as a limited company in Drammen, Buskerud with organisation number 917633002. The business is classified under visual arts creation activities (NACE 90.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivningstjenester knyttet til design av digitale produkter.”. The most recent filed accounts, for the 2024 financial year, show NOK 256,000 in revenue and NOK −179,000 in operating profit.

Key figures · 2024

Revenue
NOK 256,000
Operating profit
NOK −179,000
Equity
NOK −13,000

Financial health · 2025

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

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

Who owns TINKER STUDIO AS?

XIN LI
TINKER STUDIO AS
NOK 256,000 rev. · NOK −179,000 profit

TINKER STUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TINKER STUDIO AS

Who owns TINKER STUDIO AS?

XIN LI is the largest registered owner, with 100.0%.

What is the revenue of TINKER STUDIO AS?

TINKER STUDIO AS had revenue of NOK 256,000 in 2024.

Who is the general manager of TINKER STUDIO AS?

Xin Li is registered as general manager of TINKER STUDIO AS.

Where is TINKER STUDIO AS based?

TINKER STUDIO AS has its business address in Drammen.

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.