BIZTRAC BETA
Rental and operating of own or leased real estate

BUE BOLIGUTVIKLING OG -EIERSKAP AS

Org. no. 990145768 Limited company (AS) Lillestrøm Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −63,000
Equity NOK 359,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

BUE BOLIGUTVIKLING OG -EIERSKAP AS is registered as a limited company in Lillestrøm, Akershus with organisation number 990145768. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Boligutvikling, boligutleie, investering i fast eiendom samt deltakelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −63,000
Equity
NOK 359,000
Est. value
NOK 327,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
79.1%
Very good
Equity as a share of total capital

Who owns BUE BOLIGUTVIKLING OG -EIERSKAP AS?

JARLE BRUNSELL
BUE BOLIGUTVIKLING OG -EIERSKAP AS
· NOK −63,000 profit

BUE BOLIGUTVIKLING OG -EIERSKAP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BUE BOLIGUTVIKLING OG -EIERSKAP AS own?

BUE BOLIGUTVIKLING OG -EIERSKAP AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

BUE BOLIGUTVIKLING OG -EIERSKAP AS er morselskap for 1 datterselskap:

Frequently asked questions about BUE BOLIGUTVIKLING OG -EIERSKAP AS

Who owns BUE BOLIGUTVIKLING OG -EIERSKAP AS?

JARLE BRUNSELL is the largest registered owner, with 100.0%.

Where is BUE BOLIGUTVIKLING OG -EIERSKAP AS based?

BUE BOLIGUTVIKLING OG -EIERSKAP AS has its business address in Skjetten.

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.