BIZTRAC BETA
Repair and maintenance of footwear and leather goods

SKOMAKERMESTER VÅGE AS

Org. no. 915512852 Limited company (AS) Gjøvik Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 200,000
Equity NOK 525,000
Incorporated 2015
Share capital NOK 30,000

SKOMAKERMESTER VÅGE AS is registered as a limited company in Gjøvik, Innlandet with organisation number 915512852. The business is classified under repair and maintenance of footwear and leather goods (NACE 95.230). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Skoreparasjon, salg av sko og skopleiemidler samt salg av skinn og lær. Selskapet kan eie fast eiendom og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 200,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 200,000
Equity
NOK 525,000
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns SKOMAKERMESTER VÅGE AS?

ISAC FERGESTAD VÅGE
SKOMAKERMESTER VÅGE AS
NOK 2.6m rev. · NOK 200,000 profit

SKOMAKERMESTER VÅGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKOMAKERMESTER VÅGE AS

Who owns SKOMAKERMESTER VÅGE AS?

ISAC FERGESTAD VÅGE is the largest registered owner, with 100.0%.

What is the revenue of SKOMAKERMESTER VÅGE AS?

SKOMAKERMESTER VÅGE AS had revenue of NOK 2.6m in 2024.

Who is the general manager of SKOMAKERMESTER VÅGE AS?

Isac Fergestad Våge is registered as general manager of SKOMAKERMESTER VÅGE AS.

Where is SKOMAKERMESTER VÅGE AS based?

SKOMAKERMESTER VÅGE AS has its business address in Gjøvik.

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.