BIZTRAC BETA
Other business support service activities n.e.c.

GOOD POINT AS

Org. no. 928302296 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 8,000
Operating profit NOK −7,000
Equity NOK 81,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

GOOD POINT AS is registered as a limited company in Oslo, Oslo with organisation number 928302296. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1500 shares. The company's stated purpose is: “Konsulentvirksomhet innen salg og annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 8,000
Operating profit
NOK −7,000
Equity
NOK 81,000
Est. value
NOK 116,000

Financial health · 2024

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

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

Who owns GOOD POINT AS?

JOACHIM CHRISTIAN OVERÅ
GOOD POINT AS
NOK 8,000 rev. · NOK −7,000 profit

GOOD POINT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GOOD POINT AS

Who owns GOOD POINT AS?

JOACHIM CHRISTIAN OVERÅ is the largest registered owner, with 100.0%.

What is the revenue of GOOD POINT AS?

GOOD POINT AS had revenue of NOK 8,000 in 2024.

Who is the general manager of GOOD POINT AS?

Joachim Christian Overå is registered as general manager of GOOD POINT AS.

Where is GOOD POINT AS based?

GOOD POINT 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.