BIZTRAC BETA
Civil engineering activities

GITMARK HOLDING AS

Org. no. 991883509 Limited company (AS) Grimstad Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 779,000
Operating profit NOK 41,000
Equity NOK 4.8m
Incorporated 2007
Share capital NOK 100,000

GITMARK HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 991883509. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Deltagelse i andre selskap, rådgivningsvirksomhet og investeringsvirksomhet og utlån.”. The most recent filed accounts, for the 2024 financial year, show NOK 779,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2024

Revenue
NOK 779,000
Operating profit
NOK 41,000
Equity
NOK 4.8m
Est. value
NOK 2.6m

Financial health · 2024

Liquidity
-0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
77.9%
Very good
Equity as a share of total capital

Who owns GITMARK HOLDING AS?

TORILL OSA MICHALSEN
GITMARK HOLDING AS
NOK 779,000 rev. · NOK 41,000 profit

GITMARK HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GITMARK HOLDING AS own?

GITMARK HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about GITMARK HOLDING AS

Who owns GITMARK HOLDING AS?

TORILL OSA MICHALSEN is the largest registered owner, with 50.0%.

What is the revenue of GITMARK HOLDING AS?

GITMARK HOLDING AS had revenue of NOK 779,000 in 2024.

Who is the general manager of GITMARK HOLDING AS?

Bengt Gunnar Michalsen is registered as general manager of GITMARK HOLDING AS.

Where is GITMARK HOLDING AS based?

GITMARK HOLDING AS has its business address in Fevik.

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.