BIZTRAC BETA
Computer consultancy and computer facilities management activities

EJOHNS AS

Org. no. 918371737 Limited company (AS) Moss Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 42,000
Operating profit NOK 17,000
Equity NOK 80,000
Incorporated 2017
Share capital NOK 30,000

EJOHNS AS is registered as a limited company in Moss, Østfold with organisation number 918371737. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling, drift og salg av IT-løsninger for alle plattformer, konsulenttjenester, varehandel, kjøp og salg av aksjer , samt annen virksomhet som naturlig hører sammen med dette, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 42,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 42,000
Operating profit
NOK 17,000
Equity
NOK 80,000
Est. value
NOK 116,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EJOHNS AS?

ERIK JOHNSEN
EJOHNS AS
NOK 42,000 rev. · NOK 17,000 profit

EJOHNS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EJOHNS AS own?

EJOHNS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EJOHNS AS

Who owns EJOHNS AS?

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

What is the revenue of EJOHNS AS?

EJOHNS AS had revenue of NOK 42,000 in 2025.

Where is EJOHNS AS based?

EJOHNS AS has its business address in Moss.

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.