BIZTRAC BETA
Construction of residential and non-residential buildings

BROMA AS

Org. no. 929030559 Limited company (AS) Notodden Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 558,000
Operating profit NOK 2,000
Equity NOK 37,000
Incorporated 2022
Share capital NOK 30,000

BROMA AS is registered as a limited company in Notodden, Telemark with organisation number 929030559. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bygging av boliger og andre bygg, rehabilitering og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet. Utleie, kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 558,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2024

Revenue
NOK 558,000
Operating profit
NOK 2,000
Equity
NOK 37,000
Est. value
NOK 22,000

Financial health · 2024

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

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

Who owns BROMA AS?

EGIDIJUS STEPONAVICIUS
BROMA AS
NOK 558,000 rev. · NOK 2,000 profit

BROMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROMA AS

Who owns BROMA AS?

EGIDIJUS STEPONAVICIUS is the largest registered owner, with 100.0%.

What is the revenue of BROMA AS?

BROMA AS had revenue of NOK 558,000 in 2024.

Who is the general manager of BROMA AS?

Egidijus Steponavicius is registered as general manager of BROMA AS.

Where is BROMA AS based?

BROMA AS has its business address in Notodden.

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.