BIZTRAC BETA
Graphic design and visual communication activities

GJENSKINN GRAVMINNE AS

Org. no. 916542240 Limited company (AS) Porsgrunn Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK −10,000
Equity NOK 360,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

GJENSKINN GRAVMINNE AS is registered as a limited company in Porsgrunn, Telemark with organisation number 916542240. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikle, få produsert og selge gravminner.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK −10,000
Equity
NOK 360,000
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns GJENSKINN GRAVMINNE AS?

GITA SYNNØVE NORHEIM
GJENSKINN GRAVMINNE AS
NOK 2.6m rev. · NOK −10,000 profit

GJENSKINN GRAVMINNE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GJENSKINN GRAVMINNE AS

Who owns GJENSKINN GRAVMINNE AS?

GITA SYNNØVE NORHEIM is the largest registered owner, with 50.0%.

What is the revenue of GJENSKINN GRAVMINNE AS?

GJENSKINN GRAVMINNE AS had revenue of NOK 2.6m in 2025.

Who is the general manager of GJENSKINN GRAVMINNE AS?

Turid Uldal is registered as general manager of GJENSKINN GRAVMINNE AS.

Where is GJENSKINN GRAVMINNE AS based?

GJENSKINN GRAVMINNE AS has its business address in Porsgrunn.

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.