biztrac. BETA
COMPANY REGISTER PROFILE
913538315 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Performing arts activities in music

TRIO MEDIÆVAL AS

Org. no. 913538315 Limited company (AS) Oslo Incorporated 2014 Active
Revenue 2025 NOK 2.1m
Operating profit NOK 126,000
Equity NOK 98,000
Incorporated 2014
Share capital NOK 30,000

TRIO MEDIÆVAL AS is registered as a limited company in Oslo, Oslo with organisation number 913538315. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Formidling av musikk, samt annen virksomhet i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 126,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
▲ +38 %
Operating profit
NOK 126,000
▲ +212 %
Equity
NOK 98,000
▲ +3536 %
Est. value
NOK 538,000

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
50.2%
Very good
Return on total assets
Solidity
29.9%
Weak
Equity as a share of total capital

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

Who owns TRIO MEDIÆVAL AS?

TRIO MEDIÆVAL AS
NOK 2.1m rev. · NOK 126,000 profit

TRIO MEDIÆVAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRIO MEDIÆVAL AS

Who owns TRIO MEDIÆVAL AS?

Anna Maria Friman-Henriksen is the largest registered owner, with 50.0%.

What is the revenue of TRIO MEDIÆVAL AS?

TRIO MEDIÆVAL AS had revenue of NOK 2.1m in 2025.

Who is the general manager of TRIO MEDIÆVAL AS?

Anna Maria Friman-Henriksen is registered as general manager of TRIO MEDIÆVAL AS.

Where is TRIO MEDIÆVAL AS based?

TRIO MEDIÆVAL 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.