biztrac. BETA
COMPANY REGISTER PROFILE
913202708 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Non-specialised wholesale trade

G. O. JOHNSEN AS

Org. no. 913202708 Limited company (AS) Oslo Incorporated 1961 Active
Ownership graph ↗
Revenue 2025 NOK 40.5m
Operating profit NOK 2.1m
Equity NOK 2.3m
Incorporated 1961
Share capital NOK 2.1m

G. O. JOHNSEN AS is registered as a limited company in Oslo, Oslo with organisation number 913202708. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 1961. Registered share capital is NOK 2.1m, divided into 887 shares. The company's stated purpose is: “Forretningsdrift av enhver art, herunder agentur-, kommisjon- og engrosvirksomhet, kjøp, salg og drift av faste eiendommer, finansformidling, forsikringsagentur og forsikringsmegling.”. The most recent filed accounts, for the 2025 financial year, show NOK 40.5m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 40.5m
▼ −13 %
Operating profit
NOK 2.1m
▼ −44 %
Equity
NOK 2.3m
▼ −3 %
Est. value
NOK 10.3m

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
16.4%
Very good
Return on total assets
Solidity
6.7%
Weak
Equity as a share of total capital

Who owns G. O. JOHNSEN AS?

G. O. JOHNSEN AS
NOK 40.5m rev. · NOK 2.1m profit

G. O. JOHNSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about G. O. JOHNSEN AS

Who owns G. O. JOHNSEN AS?

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

What is the revenue of G. O. JOHNSEN AS?

G. O. JOHNSEN AS had revenue of NOK 40.5m in 2025.

Who is the general manager of G. O. JOHNSEN AS?

Siri Vandvik Johnsen is registered as general manager of G. O. JOHNSEN AS.

Where is G. O. JOHNSEN AS based?

G. O. JOHNSEN AS has its business address in Oslo.

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.