biztrac. BETA
COMPANY REGISTER PROFILE
828666622 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

GULLIKSTAD AUTO AS

Org. no. 828666622 Limited company (AS) Kongsvinger Incorporated 2022 Active
Revenue 2025 NOK 15.1m
Operating profit NOK 1.2m
Equity NOK 2.3m
Incorporated 2022
Share capital NOK 100,000

GULLIKSTAD AUTO AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 828666622. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av bruktbiler, deler, klargjøring av biler, kommisjonssalg, utleie av kjøretøy og alt som dertil hører innunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.1m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 15.1m
▲ +18 %
Operating profit
NOK 1.2m
▲ +378 %
Equity
NOK 2.3m
▲ +69 %
Est. value
NOK 5.1m

Financial health · 2025

Liquidity
2.58
Very good
Current assets ÷ current liabilities
Profitability
31.7%
Very good
Return on total assets
Solidity
59.4%
Very good
Equity as a share of total capital

Who owns GULLIKSTAD AUTO AS?

GULLIKSTAD AUTO AS
NOK 15.1m rev. · NOK 1.2m profit

GULLIKSTAD AUTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLIKSTAD AUTO AS

Who owns GULLIKSTAD AUTO AS?

Geir Ove Gullikstad is the largest registered owner, with 100.0%.

What is the revenue of GULLIKSTAD AUTO AS?

GULLIKSTAD AUTO AS had revenue of NOK 15.1m in 2025.

Who is the general manager of GULLIKSTAD AUTO AS?

Geir Ove Gullikstad is registered as general manager of GULLIKSTAD AUTO AS.

Where is GULLIKSTAD AUTO AS based?

GULLIKSTAD AUTO AS has its business address in Kongsvinger.

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.