BIZTRAC BETA
Business and other management consultancy activities

GINCO AS

Org. no. 950725095 Limited company (AS) Lillestrøm Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 406,000
Operating profit NOK −270,000
Equity NOK 9.0m
Incorporated 1989
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−270k kr).

GINCO AS is registered as a limited company in Lillestrøm, Akershus with organisation number 950725095. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handel og servicevirksomhet, tjenesteyting og produksjon, utleie av fast eiendom, deltakelse i andre selskaper, investeringer i verdipapirer, og hva der står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 406,000 in revenue and NOK −270,000 in operating profit.

Key figures · 2025

Revenue
NOK 406,000
Operating profit
NOK −270,000
Equity
NOK 9.0m
Est. value
NOK 6.4m

Financial health · 2025

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

Who owns GINCO AS?

RANDI BRITA JOHANSEN
GINCO AS
NOK 406,000 rev. · NOK −270,000 profit

GINCO AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GINCO AS

Who owns GINCO AS?

RANDI BRITA JOHANSEN is the largest registered owner, with 45.5%.

What is the revenue of GINCO AS?

GINCO AS had revenue of NOK 406,000 in 2025.

Who is the general manager of GINCO AS?

Randi Brita Johansen is registered as general manager of GINCO AS.

Where is GINCO AS based?

GINCO AS has its business address in Skedsmokorset.

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.