BIZTRAC BETA
Office administrative and support activities

GIROSERVICE AS

Org. no. 983490751 Limited company (AS) Bergen Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 395,000
Operating profit NOK −29,000
Equity NOK −32,000
Incorporated 2001
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−32k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).

GIROSERVICE AS is registered as a limited company in Bergen, Vestland with organisation number 983490751. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utsendelse av faktura, fakturaadministrasjon og andre tjenester som faller naturlig innenfor virksomhetsområdet, samt utleie og kjøp av eiendom, samt hva dermed hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 395,000 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 395,000
Operating profit
NOK −29,000
Equity
NOK −32,000

Financial health · 2025

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-34.4%
Weak
Equity as a share of total capital

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

Who owns GIROSERVICE AS?

Helle Svenkerud
GIROSERVICE AS
NOK 395,000 rev. · NOK −29,000 profit

GIROSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GIROSERVICE AS

Who owns GIROSERVICE AS?

Helle Svenkerud is the largest registered owner, with 100.0%.

What is the revenue of GIROSERVICE AS?

GIROSERVICE AS had revenue of NOK 395,000 in 2025.

Where is GIROSERVICE AS based?

GIROSERVICE AS has its business address in Paradis.

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.