BIZTRAC BETA
Computer programming activities

ERIK GULLIKSEN AS

Org. no. 915440479 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 1.3m
Equity NOK 4.0m
Incorporated 2015
Share capital NOK 30,000

ERIK GULLIKSEN AS is registered as a limited company in Bærum, Akershus with organisation number 915440479. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet innen systemutvikling og design. Egen produktutvikling. Trading og investeringsaktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 1.3m
Equity
NOK 4.0m
Est. value
NOK 6.7m

Financial health · 2025

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

Who owns ERIK GULLIKSEN AS?

ERIK GULLIKSEN
ERIK GULLIKSEN AS
NOK 2.4m rev. · NOK 1.3m profit

ERIK GULLIKSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERIK GULLIKSEN AS own?

ERIK GULLIKSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ERIK GULLIKSEN AS

Who owns ERIK GULLIKSEN AS?

ERIK GULLIKSEN is the largest registered owner, with 100.0%.

What is the revenue of ERIK GULLIKSEN AS?

ERIK GULLIKSEN AS had revenue of NOK 2.4m in 2025.

Who is the general manager of ERIK GULLIKSEN AS?

Erik Gulliksen is registered as general manager of ERIK GULLIKSEN AS.

Where is ERIK GULLIKSEN AS based?

ERIK GULLIKSEN AS has its business address in Hø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.