BIZTRAC BETA
Rental and operating of own or leased real estate

NEVLUNGHAVN GJESTGIVERI AS

Org. no. 847667052 Limited company (AS) Larvik Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −465,000
Equity NOK 4.3m
Incorporated 1988
Share capital NOK 707,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−465k kr).

NEVLUNGHAVN GJESTGIVERI AS is registered as a limited company in Larvik, Vestfold with organisation number 847667052. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988. Registered share capital is NOK 707,000, divided into 700 shares. The company's stated purpose is: “Å drive bevertnings- og losjivirksomhet og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −465,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −465,000
Equity
NOK 4.3m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns NEVLUNGHAVN GJESTGIVERI AS?

IAPETOS AS
NEVLUNGHAVN GJESTGIVERI AS
NOK 1.0m rev. · NOK −465,000 profit

NEVLUNGHAVN GJESTGIVERI AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NEVLUNGHAVN GJESTGIVERI AS er morselskap for 1 datterselskap:

Frequently asked questions about NEVLUNGHAVN GJESTGIVERI AS

Who owns NEVLUNGHAVN GJESTGIVERI AS?

IAPETOS AS is the largest registered owner, with 100.0%.

What is the revenue of NEVLUNGHAVN GJESTGIVERI AS?

NEVLUNGHAVN GJESTGIVERI AS had revenue of NOK 1.0m in 2025.

Where is NEVLUNGHAVN GJESTGIVERI AS based?

NEVLUNGHAVN GJESTGIVERI AS has its business address in Nevlunghavn.

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.