BIZTRAC BETA
Rental and operating of own or leased real estate

GNEISVEIEN 8 AS

Org. no. 816067782 Limited company (AS) Sandefjord Incorporated 1959 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 819,000
Equity NOK 2.1m
Incorporated 1959
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GNEISVEIEN 8 AS is registered as a limited company in Sandefjord, Vestfold with organisation number 816067782. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1959. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom, eie fast eiendom, eiendomsutvikling, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 819,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 819,000
Equity
NOK 2.1m
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns GNEISVEIEN 8 AS?

GNEISVEIEN 8 HOLDING AS
GNEISVEIEN 8 AS
NOK 2.4m rev. · NOK 819,000 profit

GNEISVEIEN 8 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GNEISVEIEN 8 AS

Who owns GNEISVEIEN 8 AS?

GNEISVEIEN 8 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GNEISVEIEN 8 AS?

GNEISVEIEN 8 AS had revenue of NOK 2.4m in 2024.

Where is GNEISVEIEN 8 AS based?

GNEISVEIEN 8 AS has its business address in Sandefjord.

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.