BIZTRAC BETA
Sound recording and music publishing activities

TOOTHFAIRY PUBLISHING AS

Org. no. 933030075 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 27,000
Operating profit NOK 9,000
Equity NOK 32,000
Incorporated 2024
Share capital NOK 30,000

TOOTHFAIRY PUBLISHING AS is registered as a limited company in Bærum, Akershus with organisation number 933030075. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “kjøpe, selge og forvalte publiseringsrettigheter og alt som står i den forbindelse inkludert å gjøre seg interessert i selskaper og innretninger som driver med det samme.”. The most recent filed accounts, for the 2024 financial year, show NOK 27,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2024

Revenue
NOK 27,000
Operating profit
NOK 9,000
Equity
NOK 32,000
Est. value
NOK 58,000

Financial health · 2024

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

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

Who owns TOOTHFAIRY PUBLISHING AS?

TOOTHFAIRY AS
TOOTHFAIRY PUBLISHING AS
NOK 27,000 rev. · NOK 9,000 profit

TOOTHFAIRY PUBLISHING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOOTHFAIRY PUBLISHING AS

Who owns TOOTHFAIRY PUBLISHING AS?

TOOTHFAIRY AS is the largest registered owner, with 100.0%.

What is the revenue of TOOTHFAIRY PUBLISHING AS?

TOOTHFAIRY PUBLISHING AS had revenue of NOK 27,000 in 2024.

Where is TOOTHFAIRY PUBLISHING AS based?

TOOTHFAIRY PUBLISHING AS has its business address in Sandvika.

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.