BIZTRAC BETA
Business and other management consultancy activities

BUZZARD CONSULTING AS

Org. no. 920275400 Limited company (AS) Evenes Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 12,000
Operating profit NOK 3,000
Equity NOK 132,000
Incorporated 2018
Share capital NOK 30,000

BUZZARD CONSULTING AS is registered as a limited company in Evenes, Nordland with organisation number 920275400. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet og rådgiving innen informasjon, administrasjon, samfunnskontakt og lobbyering, samt annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 12,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 12,000
Operating profit
NOK 3,000
Equity
NOK 132,000
Est. value
NOK 77,000

Financial health · 2025

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

Who owns BUZZARD CONSULTING AS?

JARDAR JENSEN
BUZZARD CONSULTING AS
NOK 12,000 rev. · NOK 3,000 profit

BUZZARD CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BUZZARD CONSULTING AS own?

BUZZARD CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BUZZARD CONSULTING AS

Who owns BUZZARD CONSULTING AS?

JARDAR JENSEN is the largest registered owner, with 100.0%.

What is the revenue of BUZZARD CONSULTING AS?

BUZZARD CONSULTING AS had revenue of NOK 12,000 in 2025.

Where is BUZZARD CONSULTING AS based?

BUZZARD CONSULTING AS has its business address in Liland.

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.