BIZTRAC BETA
Work training and permanently adapted work

BRA-PRO LURØY KOMMUNALE VTA AS

Org. no. 958675070 Limited company (AS) Lurøy Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK 728,000
Equity NOK 9.5m
Incorporated 1990
Employees 33
Share capital NOK 1.4m

BRA-PRO LURØY KOMMUNALE VTA AS is registered as a limited company in Lurøy, Nordland with organisation number 958675070. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 1990 and has 33 registered employees. Registered share capital is NOK 1.4m, divided into 14000 shares. The company's stated purpose is: “Håndverksmessig produksjon og forestå andre tjenester etter sosialpedagogiske kriterier som vernet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK 728,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK 728,000
Equity
NOK 9.5m
Est. value
NOK 10.0m

Financial health · 2024

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

Who owns BRA-PRO LURØY KOMMUNALE VTA AS?

No shareholders are registered for BRA-PRO LURØY KOMMUNALE VTA AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BRA-PRO LURØY KOMMUNALE VTA AS

What is the revenue of BRA-PRO LURØY KOMMUNALE VTA AS?

BRA-PRO LURØY KOMMUNALE VTA AS had revenue of NOK 6.8m in 2024.

Who is the general manager of BRA-PRO LURØY KOMMUNALE VTA AS?

Morten Jostein Aspdal Olsen is registered as general manager of BRA-PRO LURØY KOMMUNALE VTA AS.

Where is BRA-PRO LURØY KOMMUNALE VTA AS based?

BRA-PRO LURØY KOMMUNALE VTA AS has its business address in Aldersundet.

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.