BIZTRAC BETA
Rental and operating of own or leased real estate

BROMSTADVEIEN 57 AS

Org. no. 983484182 Limited company (AS) Trondheim Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 1.4m
Equity NOK 4.2m
Incorporated 2001
Share capital NOK 105,000

BROMSTADVEIEN 57 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 983484182. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 105,000, divided into 105 shares. The company's stated purpose is: “Kjøp, salg, videreutvikling og utleie av fast eiendom samt annen virksomhet som naturlig står i forbindelse med dette, herunder å delta i andre selskaper med liknende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 1.4m
Equity
NOK 4.2m
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.8%
Good
Equity as a share of total capital

Who owns BROMSTADVEIEN 57 AS?

BYGGMESTER KARL BEKKEN AS
BROMSTADVEIEN 57 AS
NOK 2.0m rev. · NOK 1.4m profit

BROMSTADVEIEN 57 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROMSTADVEIEN 57 AS

Who owns BROMSTADVEIEN 57 AS?

BYGGMESTER KARL BEKKEN AS is the largest registered owner, with 100.0%.

What is the revenue of BROMSTADVEIEN 57 AS?

BROMSTADVEIEN 57 AS had revenue of NOK 2.0m in 2025.

Who is the general manager of BROMSTADVEIEN 57 AS?

Karl Bekken is registered as general manager of BROMSTADVEIEN 57 AS.

Where is BROMSTADVEIEN 57 AS based?

BROMSTADVEIEN 57 AS has its business address in Trondheim.

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.