BIZTRAC BETA
Retail sale of clothing

GRAN HERREEKVIPERING AS

Org. no. 912040798 Limited company (AS) Gran Incorporated 1981 Active
Ownership graph ↗
Revenue 2025 NOK 8.0m
Operating profit NOK 957,000
Equity NOK 3.3m
Incorporated 1981
Share capital NOK 100,000

GRAN HERREEKVIPERING AS is registered as a limited company in Gran, Innlandet with organisation number 912040798. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 1981. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Handel, agentur og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.0m in revenue and NOK 957,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.0m
Operating profit
NOK 957,000
Equity
NOK 3.3m
Est. value
NOK 5.1m

Financial health · 2025

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

Who owns GRAN HERREEKVIPERING AS?

MIKAL LINSTAD
GRAN HERREEKVIPERING AS
NOK 8.0m rev. · NOK 957,000 profit

GRAN HERREEKVIPERING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GRAN HERREEKVIPERING AS own?

GRAN HERREEKVIPERING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GRAN HERREEKVIPERING AS

Who owns GRAN HERREEKVIPERING AS?

MIKAL LINSTAD is the largest registered owner, with 100.0%.

What is the revenue of GRAN HERREEKVIPERING AS?

GRAN HERREEKVIPERING AS had revenue of NOK 8.0m in 2025.

Who is the general manager of GRAN HERREEKVIPERING AS?

Mikal Linstad is registered as general manager of GRAN HERREEKVIPERING AS.

Where is GRAN HERREEKVIPERING AS based?

GRAN HERREEKVIPERING AS has its business address in Gran.

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.