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

VIBBEFANGER AS

Org. no. 918738436 Limited company (AS) Oslo Incorporated 2017 Active
Revenue 2025 NOK 278,000
Operating profit NOK 168,000
Equity NOK 391,000
Incorporated 2017
Share capital NOK 30,000

VIBBEFANGER AS is registered as a limited company in Oslo, Oslo with organisation number 918738436. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forvalte artistkarrieren til artister i Vibbefanger. Vibbefanger skal formidle musikk gjennom utgivelser, konserter, klubb, festivaler, radio og TV. Salg av musikk gjennom de kanaler som til enhver tid er aktuelle i markedet. Vi skal skape en plattform for utfoldelse som kan engasjere unge kreative.”. The most recent filed accounts, for the 2025 financial year, show NOK 278,000 in revenue and NOK 168,000 in operating profit.

Key figures · 2025

Revenue
NOK 278,000
▼ −42 %
Operating profit
NOK 168,000
▲ +1336 %
Equity
NOK 391,000
▲ +77 %
Est. value
NOK 673,000

Financial health · 2025

Liquidity
43.18
Very good
Current assets ÷ current liabilities
Profitability
54.9%
Very good
Return on total assets
Solidity
97.7%
Very good
Equity as a share of total capital

Who owns VIBBEFANGER AS?

VIBBEFANGER AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIBBEFANGER AS

Who owns VIBBEFANGER AS?

Bendik Martinus Notøy is the largest registered owner, with 12.5%.

What is the revenue of VIBBEFANGER AS?

VIBBEFANGER AS had revenue of NOK 278,000 in 2025.

Where is VIBBEFANGER AS based?

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