BIZTRAC BETA
Legal activities

BRULAND BINGE AS

Org. no. 918916032 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 364,000
Operating profit NOK −417,000
Equity NOK 605,000
Incorporated 2017
Share capital NOK 101,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−417k kr).

BRULAND BINGE AS is registered as a limited company in Bergen, Vestland with organisation number 918916032. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2017. Registered share capital is NOK 101,000, divided into 100000 shares. The company's stated purpose is: “Selskapets formål er: Å eie aksjer i andre selskaper og annen investeringsvirksomhet, herunder investering i travhester og tilknyttet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 364,000 in revenue and NOK −417,000 in operating profit.

Key figures · 2024

Revenue
NOK 364,000
Operating profit
NOK −417,000
Equity
NOK 605,000
Est. value
NOK 982,000

Financial health · 2024

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

Who owns BRULAND BINGE AS?

GRUNDE BRULAND
BRULAND BINGE AS
NOK 364,000 rev. · NOK −417,000 profit

BRULAND BINGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BRULAND BINGE AS own?

BRULAND BINGE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BRULAND BINGE AS

Who owns BRULAND BINGE AS?

GRUNDE BRULAND is the largest registered owner, with 100.0%.

What is the revenue of BRULAND BINGE AS?

BRULAND BINGE AS had revenue of NOK 364,000 in 2024.

Where is BRULAND BINGE AS based?

BRULAND BINGE AS has its business address in Søreidgrend.

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.