biztrac. BETA
COMPANY REGISTER PROFILE
935303117 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Sound recording and music publishing activities

TERRAPRETA AS

Org. no. 935303117 Limited company (AS) Oslo Incorporated 2025 Active
Revenue 2025 NOK 215,000
Operating profit NOK 5,000
Equity NOK 28,000
Incorporated 2025
Share capital NOK 30,000

TERRAPRETA AS is registered as a limited company in Oslo, Oslo with organisation number 935303117. The business is classified under sound recording and music publishing activities (NACE 59.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 utgivelse av musikk og lyd, import av varer og transporttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 215,000 in revenue and NOK 5,000 in operating profit.

Former names: AMP MUSIC & RECORDS AS

Key figures · 2025

Revenue
NOK 215,000
Operating profit
NOK 5,000
Equity
NOK 28,000
Est. value
NOK 42,000

Financial health · 2025

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

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

Who owns TERRAPRETA AS?

TERRAPRETA AS
NOK 215,000 rev. · NOK 5,000 profit

TERRAPRETA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TERRAPRETA AS

Who owns TERRAPRETA AS?

Anders Åke Roland Thorén is the largest registered owner, with 100.0%.

What is the revenue of TERRAPRETA AS?

TERRAPRETA AS had revenue of NOK 215,000 in 2025.

Who is the general manager of TERRAPRETA AS?

Anders Åke Roland Thorén is registered as general manager of TERRAPRETA AS.

Where is TERRAPRETA AS based?

TERRAPRETA 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.