BIZTRAC BETA
Buying and selling of own real estate

GLOVA AS

Org. no. 989406736 Limited company (AS) Færder Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 4,000
Operating profit NOK −13,000
Equity NOK 1.1m
Incorporated 2006
Share capital NOK 100,000

Signals

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

GLOVA AS is registered as a limited company in Færder, Vestfold with organisation number 989406736. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eiendoms- og aksjeinvesteringer og hva som naturlig hører sammen med dette, deltakelse i andre selskaper, samt utlånsvirksomhet og garantistillelser.”. The most recent filed accounts, for the 2024 financial year, show NOK 4,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 4,000
Operating profit
NOK −13,000
Equity
NOK 1.1m
Est. value
NOK 748,000

Financial health · 2024

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

Who owns GLOVA AS?

PAAL STENBERG
GLOVA AS
NOK 4,000 rev. · NOK −13,000 profit

GLOVA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GLOVA AS own?

GLOVA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GLOVA AS

Who owns GLOVA AS?

PAAL STENBERG is the largest registered owner, with 100.0%.

What is the revenue of GLOVA AS?

GLOVA AS had revenue of NOK 4,000 in 2024.

Who is the general manager of GLOVA AS?

Paal Stenberg is registered as general manager of GLOVA AS.

Where is GLOVA AS based?

GLOVA AS has its business address in Husøysund.

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.