biztrac. BETA
COMPANY REGISTER PROFILE
921006624 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

GVELVEN FERIEGREND AS

Org. no. 921006624 Limited company (AS) Fredrikstad Incorporated 2018 Active
Operating profit NOK −143,000
Equity NOK −1.2m
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,2 mill kr).

GVELVEN FERIEGREND AS is registered as a limited company in Fredrikstad, Østfold with organisation number 921006624. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Oppføring av hytter/leiligheter for salg og utleie med salg av produkter og tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −143,000
▲ +96 %
Equity
NOK −1.2m
▼ −26 %

Financial health · 2025

Liquidity
3.30
Very good
Current assets ÷ current liabilities
Profitability
-1.1%
Not satisfactory
Return on total assets
Solidity
-9.2%
Weak
Equity as a share of total capital

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

Who owns GVELVEN FERIEGREND AS?

GVELVEN FERIEGREND AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GVELVEN FERIEGREND AS

Who owns GVELVEN FERIEGREND AS?

Øystein Gjellerud is the largest registered owner, with 50.0%.

Who is the general manager of GVELVEN FERIEGREND AS?

Svend Erik Lilleby is registered as general manager of GVELVEN FERIEGREND AS.

Where is GVELVEN FERIEGREND AS based?

GVELVEN FERIEGREND AS has its business address in Gressvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.