BIZTRAC BETA
Computer programming activities

GIVN NORGE AS

Org. no. 927405938 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK −4.5m
Equity NOK 7.5m
Incorporated 2021
Employees 5
Share capital NOK 82,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,5 mill kr).

GIVN NORGE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927405938. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 82,000, divided into 82031 shares. The company's stated purpose is: “Utvikler og tilbyr digitale transaksjonsløsninger, bla. en gavekortløsning for kjøp og salg av digitale gavekort. Selskapet kan også eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK −4.5m in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK −4.5m
Equity
NOK 7.5m
Est. value
NOK 13.6m

Financial health · 2024

Liquidity
1.97
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.6%
Good
Equity as a share of total capital

Who owns GIVN NORGE AS?

GIVN HOLDING AS
GIVN NORGE AS
NOK 4.6m rev. · NOK −4.5m profit

GIVN NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GIVN NORGE AS

Who owns GIVN NORGE AS?

GIVN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GIVN NORGE AS?

GIVN NORGE AS had revenue of NOK 4.6m in 2024.

Who is the general manager of GIVN NORGE AS?

Erlend Solum Ledang is registered as general manager of GIVN NORGE AS.

Where is GIVN NORGE AS based?

GIVN NORGE AS has its business address in Trondheim.

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.