BIZTRAC BETA
Uoppgitt

BM GILJE HOLDING AS

Org. no. 932986817 Limited company (AS) Time Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 14,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

BM GILJE HOLDING AS is registered as a limited company in Time, Rogaland with organisation number 932986817. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt 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 foretagende.”.

Key figures · 2025

Operating profit
NOK −14,000
Equity
NOK 14,000
Est. value
NOK 17,000

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.3%
Weak
Equity as a share of total capital

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

Who owns BM GILJE HOLDING AS?

BERGLJOT MOLAUG GILJE
BM GILJE HOLDING AS
· NOK −14,000 profit

BM GILJE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BM GILJE HOLDING AS own?

BM GILJE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BM GILJE HOLDING AS

Who owns BM GILJE HOLDING AS?

BERGLJOT MOLAUG GILJE is the largest registered owner, with 100.0%.

Who is the general manager of BM GILJE HOLDING AS?

Bergljot Molaug Gilje is registered as general manager of BM GILJE HOLDING AS.

Where is BM GILJE HOLDING AS based?

BM GILJE HOLDING AS has its business address in Lye.

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.