BIZTRAC BETA
Public relations and communication activities

BUZZ PR AS

Org. no. 912284417 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 838,000
Operating profit NOK 1,000
Equity NOK 52,000
Incorporated 2013
Share capital NOK 30,000

BUZZ PR AS is registered as a limited company in Oslo, Oslo with organisation number 912284417. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentbistand innen kommunikasjon, marketing og public relations og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 838,000 in revenue and NOK 1,000 in operating profit.

Key figures · 2025

Revenue
NOK 838,000
Operating profit
NOK 1,000
Equity
NOK 52,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns BUZZ PR AS?

LINDA VASQUEZ
BUZZ PR AS
NOK 838,000 rev. · NOK 1,000 profit

BUZZ PR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUZZ PR AS

Who owns BUZZ PR AS?

LINDA VASQUEZ is the largest registered owner, with 100.0%.

What is the revenue of BUZZ PR AS?

BUZZ PR AS had revenue of NOK 838,000 in 2025.

Who is the general manager of BUZZ PR AS?

Linda Vasquez is registered as general manager of BUZZ PR AS.

Where is BUZZ PR AS based?

BUZZ PR 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 15.06.2026.

Report a problem

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