BIZTRAC BETA
Rental and operating of own or leased real estate

NULANDSVIKA 1 AS

Org. no. 995573830 Limited company (AS) Flekkefjord Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 1.4m
Equity NOK 3.0m
Incorporated 2010
Share capital NOK 1.7m

Signals

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

NULANDSVIKA 1 AS is registered as a limited company in Flekkefjord, Agder with organisation number 995573830. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 1.7m, divided into 1700 shares. The company's stated purpose is: “Utvikling og utleie av fast eiendom, samt delta i andre selskap med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 1.4m
Equity
NOK 3.0m
Est. value
NOK 3.0m

Financial health · 2024

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.1%
Satisfactory
Equity as a share of total capital

Who owns NULANDSVIKA 1 AS?

EGENES HOLDING AS
NULANDSVIKA 1 AS
NOK 2.8m rev. · NOK 1.4m profit

NULANDSVIKA 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NULANDSVIKA 1 AS

Who owns NULANDSVIKA 1 AS?

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

What is the revenue of NULANDSVIKA 1 AS?

NULANDSVIKA 1 AS had revenue of NOK 2.8m in 2024.

Who is the general manager of NULANDSVIKA 1 AS?

Stein Asgeir Egenes is registered as general manager of NULANDSVIKA 1 AS.

Where is NULANDSVIKA 1 AS based?

NULANDSVIKA 1 AS has its business address in Flekkefjord.

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.