BIZTRAC BETA
Manufacture of metal structures and parts of structures

Beko industriverksted A/S

Org. no. 945895659 Limited company (AS) Bodø Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 17.5m
Operating profit NOK 207,000
Equity NOK 3.4m
Incorporated 1987
Employees 16
Share capital NOK 1.4m

Beko industriverksted A/S is registered as a limited company in Bodø, Nordland with organisation number 945895659. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 1987 and has 16 registered employees. Registered share capital is NOK 1.4m, divided into 1380 shares. The company's stated purpose is: “Verksteddrift og oppføring av industribygg, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.5m in revenue and NOK 207,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.5m
Operating profit
NOK 207,000
Equity
NOK 3.4m
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns Beko industriverksted A/S?

KEBO EIENDOM AS
Beko industriverksted A/S
NOK 17.5m rev. · NOK 207,000 profit

Beko industriverksted A/S has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about Beko industriverksted A/S

Who owns Beko industriverksted A/S?

KEBO EIENDOM AS is the largest registered owner, with 48.7%.

What is the revenue of Beko industriverksted A/S?

Beko industriverksted A/S had revenue of NOK 17.5m in 2024.

Who is the general manager of Beko industriverksted A/S?

Gøran Thuv is registered as general manager of Beko industriverksted A/S.

Where is Beko industriverksted A/S based?

Beko industriverksted A/S has its business address in Bodø.

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.