BIZTRAC BETA
Business and other management consultancy activities

STUDIO KOTTE AS

Org. no. 915703879 Limited company (AS) Øksnes Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 90,000
Equity NOK 305,000
Incorporated 2015
Share capital NOK 30,000

STUDIO KOTTE AS is registered as a limited company in Øksnes, Nordland with organisation number 915703879. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Selge konsulenttjenester, kurs og foredrag innen ledelse og sosial bærekraft.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 90,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 90,000
Equity
NOK 305,000
Est. value
NOK 644,000

Financial health · 2025

Liquidity
3.52
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
73.1%
Very good
Equity as a share of total capital

Who owns STUDIO KOTTE AS?

KRISTINE KOTTE-ERIKSEN
STUDIO KOTTE AS
NOK 1.0m rev. · NOK 90,000 profit

STUDIO KOTTE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STUDIO KOTTE AS own?

STUDIO KOTTE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STUDIO KOTTE AS

Who owns STUDIO KOTTE AS?

KRISTINE KOTTE-ERIKSEN is the largest registered owner, with 100.0%.

What is the revenue of STUDIO KOTTE AS?

STUDIO KOTTE AS had revenue of NOK 1.0m in 2025.

Who is the general manager of STUDIO KOTTE AS?

Kristine Kotte-Eriksen is registered as general manager of STUDIO KOTTE AS.

Where is STUDIO KOTTE AS based?

STUDIO KOTTE AS has its business address in Myre.

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.