BIZTRAC BETA
Rental and operating of own or leased real estate

BROMSVEIEN 31 AS

Org. no. 930080144 Limited company (AS) Horten Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 160,000
Operating profit NOK 13,000
Equity NOK 35,000
Incorporated 2022
Share capital NOK 30,000

BROMSVEIEN 31 AS is registered as a limited company in Horten, Vestfold with organisation number 930080144. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i verdipapirer og eiendom, eiendomsdrift og konsulenttjenester samt hva som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 160,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 160,000
Operating profit
NOK 13,000
Equity
NOK 35,000
Est. value
NOK 44,000

Financial health · 2025

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

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

Who owns BROMSVEIEN 31 AS?

ERLEND MORLAND HOLDING AS
BROMSVEIEN 31 AS
NOK 160,000 rev. · NOK 13,000 profit

BROMSVEIEN 31 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROMSVEIEN 31 AS

Who owns BROMSVEIEN 31 AS?

ERLEND MORLAND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BROMSVEIEN 31 AS?

BROMSVEIEN 31 AS had revenue of NOK 160,000 in 2025.

Who is the general manager of BROMSVEIEN 31 AS?

Erlend Nicolay Morland is registered as general manager of BROMSVEIEN 31 AS.

Where is BROMSVEIEN 31 AS based?

BROMSVEIEN 31 AS has its business address in Horten.

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.