BIZTRAC BETA
Computer consultancy and computer facilities management activities

TIND STUDIO AS

Org. no. 835219682 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 57,000
Equity NOK 71,000
Incorporated 2025
Share capital NOK 30,000

TIND STUDIO AS is registered as a limited company in Oslo, Oslo with organisation number 835219682. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 57,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 57,000
Equity
NOK 71,000
Est. value
NOK 512,000

Financial health · 2025

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

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

Who owns TIND STUDIO AS?

SKAVL 1 AS
TIND STUDIO AS
NOK 1.7m rev. · NOK 57,000 profit

TIND STUDIO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIND STUDIO AS

Who owns TIND STUDIO AS?

SKAVL 1 AS is the largest registered owner, with 75.0%.

What is the revenue of TIND STUDIO AS?

TIND STUDIO AS had revenue of NOK 1.7m in 2025.

Who is the general manager of TIND STUDIO AS?

Joakim Trinerud Rognlien is registered as general manager of TIND STUDIO AS.

Where is TIND STUDIO AS based?

TIND STUDIO 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.