BIZTRAC BETA
Development of building projects

BREIBUKT ULLENSAKER AS

Org. no. 920328016 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −249,000
Equity NOK 5.2m
Incorporated 2018
Share capital NOK 5.2m

Signals

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

BREIBUKT ULLENSAKER AS is registered as a limited company in Oslo, Oslo with organisation number 920328016. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 5.2m, divided into 520000 shares. The company's stated purpose is: “Investeringsvirksomhet av aksjer og andre finansielle instrumenter, samt eiendomsutvikling og dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −249,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −249,000
Equity
NOK 5.2m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns BREIBUKT ULLENSAKER AS?

BREIBUKT HOLDING AS
BREIBUKT ULLENSAKER AS
NOK 0 rev. · NOK −249,000 profit

BREIBUKT ULLENSAKER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BREIBUKT ULLENSAKER AS

Who owns BREIBUKT ULLENSAKER AS?

BREIBUKT HOLDING AS is the largest registered owner, with 95.0%.

What is the revenue of BREIBUKT ULLENSAKER AS?

BREIBUKT ULLENSAKER AS had revenue of NOK 0 in 2024.

Where is BREIBUKT ULLENSAKER AS based?

BREIBUKT ULLENSAKER AS has its business address in Oslo.

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.