biztrac. BETA
COMPANY REGISTER PROFILE
823096062 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Non-specialised retail sale of predominately food, beverages or tobacco

GILJA SNARKJØP AS

Org. no. 823096062 Limited company (AS) Gjesdal Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 23.4m
Operating profit NOK 868,000
Equity NOK 2.3m
Incorporated 2019
Employees 11
Share capital NOK 100,000

GILJA SNARKJØP AS is registered as a limited company in Gjesdal, Rogaland with organisation number 823096062. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2019 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Dagligvarehandel samt alt som står i forbindelse med dette, herunder deltakelse i annen virksomhet med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.4m in revenue and NOK 868,000 in operating profit.

Former names: NYE GILJA SNARKJØP AS

Key figures · 2025

Revenue
NOK 23.4m
▼ −13 %
Operating profit
NOK 868,000
▲ +422 %
Equity
NOK 2.3m
▲ +42 %
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
1.76
Good
Current assets ÷ current liabilities
Profitability
19.6%
Very good
Return on total assets
Solidity
48.0%
Very good
Equity as a share of total capital

Who owns GILJA SNARKJØP AS?

GILJA SNARKJØP AS
NOK 23.4m rev. · NOK 868,000 profit

GILJA SNARKJØP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GILJA SNARKJØP AS

Who owns GILJA SNARKJØP AS?

AVALO AS is the largest registered owner, with 100.0%.

What is the revenue of GILJA SNARKJØP AS?

GILJA SNARKJØP AS had revenue of NOK 23.4m in 2025.

Where is GILJA SNARKJØP AS based?

GILJA SNARKJØP AS has its business address in Dirdal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.