BIZTRAC BETA
Other support activities to arts and performing arts

TJUKK AS

Org. no. 913639499 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 7,000
Equity NOK 46,000
Incorporated 2014
Share capital NOK 30,000

TJUKK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 913639499. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Levere tjenester innen lyd/lys/sceneteknikk og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 7,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 7,000
Equity
NOK 46,000
Est. value
NOK 59,000

Financial health · 2024

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

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

Who owns TJUKK AS?

KETIL NICOLAYSEN
TJUKK AS
NOK 1.1m rev. · NOK 7,000 profit

TJUKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TJUKK AS

Who owns TJUKK AS?

KETIL NICOLAYSEN is the largest registered owner, with 100.0%.

What is the revenue of TJUKK AS?

TJUKK AS had revenue of NOK 1.1m in 2024.

Who is the general manager of TJUKK AS?

Ketil Nicolaysen is registered as general manager of TJUKK AS.

Where is TJUKK AS based?

TJUKK AS has its business address in Trondheim.

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.