BIZTRAC BETA
Manufacture of other general-purpose machinery n.e.c.

BIDNE MEK & SVEIS AS

Org. no. 984223749 Limited company (AS) Voss Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 7.0m
Operating profit NOK 525,000
Equity NOK 1.9m
Incorporated 2002
Share capital NOK 100,000

BIDNE MEK & SVEIS AS is registered as a limited company in Voss, Vestland with organisation number 984223749. The business is classified under manufacture of other general-purpose machinery n.e.c. (NACE 28.290). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Mekanisk produksjon og reparasjon samt drift av gartneri. Selskapet kan også gjennom aksjekjøp eller på andre måtar engasjere seg i andre føretak uansett føremål og selskapsform.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.0m in revenue and NOK 525,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.0m
Operating profit
NOK 525,000
Equity
NOK 1.9m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns BIDNE MEK & SVEIS AS?

JON HORVEI
BIDNE MEK & SVEIS AS
NOK 7.0m rev. · NOK 525,000 profit

BIDNE MEK & SVEIS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIDNE MEK & SVEIS AS

Who owns BIDNE MEK & SVEIS AS?

JON HORVEI is the largest registered owner, with 50.0%.

What is the revenue of BIDNE MEK & SVEIS AS?

BIDNE MEK & SVEIS AS had revenue of NOK 7.0m in 2025.

Who is the general manager of BIDNE MEK & SVEIS AS?

Joar Bidne Horvei is registered as general manager of BIDNE MEK & SVEIS AS.

Where is BIDNE MEK & SVEIS AS based?

BIDNE MEK & SVEIS AS has its business address in Vossestrand.

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.