BIZTRAC BETA
Other technical consultancy

VOGELSANG NORGE AS

Org. no. 931719572 Limited company (AS) Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 19.5m
Operating profit NOK 985,000
Equity NOK 1.7m
Incorporated 2023
Share capital NOK 1.0m

VOGELSANG NORGE AS is registered as a limited company in Hå, Rogaland with organisation number 931719572. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Salg og service av morselskapets produkter innen industri, kloakk, landbruk, skipsfart og jernbane, særlig pumper og annen teknologi i denne forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.5m in revenue and NOK 985,000 in operating profit.

Key figures · 2024

Revenue
NOK 19.5m
Operating profit
NOK 985,000
Equity
NOK 1.7m
Est. value
NOK 5.8m

Financial health · 2024

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.3%
Good
Equity as a share of total capital

Who owns VOGELSANG NORGE AS?

HUGO VOGELSANG MASCHINENBAU GNBH
VOGELSANG NORGE AS
NOK 19.5m rev. · NOK 985,000 profit

VOGELSANG NORGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VOGELSANG NORGE AS er morselskap for 1 datterselskap:

Frequently asked questions about VOGELSANG NORGE AS

Who owns VOGELSANG NORGE AS?

HUGO VOGELSANG MASCHINENBAU GNBH is the largest registered owner, with 100.0%.

What is the revenue of VOGELSANG NORGE AS?

VOGELSANG NORGE AS had revenue of NOK 19.5m in 2024.

Who is the general manager of VOGELSANG NORGE AS?

Svein Søyland is registered as general manager of VOGELSANG NORGE AS.

Where is VOGELSANG NORGE AS based?

VOGELSANG NORGE AS has its business address in Nærbø.

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.