BIZTRAC BETA
Activities of advertising agencies

BROKKE AS

Org. no. 995710773 Limited company (AS) Valle Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK −463,000
Equity NOK 594,000
Incorporated 2010
Employees 6
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−463k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BROKKE AS is registered as a limited company in Valle, Agder with organisation number 995710773. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2010 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drift og utvikling av Brokke som destinasjon, samt alt som naturlig følger med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK −463,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK −463,000
Equity
NOK 594,000
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
1.86
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
58.7%
Very good
Equity as a share of total capital

Who owns BROKKE AS?

BROKKE EIGEDOM AS
BROKKE AS
NOK 1.3m rev. · NOK −463,000 profit

BROKKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROKKE AS

Who owns BROKKE AS?

BROKKE EIGEDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BROKKE AS?

BROKKE AS had revenue of NOK 1.3m in 2024.

Who is the general manager of BROKKE AS?

Harald Eikrem Andersen is registered as general manager of BROKKE AS.

Where is BROKKE AS based?

BROKKE AS has its business address in Rysstad.

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.