BIZTRAC BETA
Rental and operating of own or leased real estate

NANSETGATA 23 AS

Org. no. 927830469 Limited company (AS) Larvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 527,000
Operating profit NOK 31,000
Equity NOK 356,000
Incorporated 2021
Share capital NOK 30,000

NANSETGATA 23 AS is registered as a limited company in Larvik, Vestfold with organisation number 927830469. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Pensjonat. Produksjon av lokalmat, kunst og designvarer for salg. Investering i aksjer og andre eierandeler i andre selskaper og fast eiendom, samt forvaltning av fast eiendom, og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 527,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2025

Revenue
NOK 527,000
Operating profit
NOK 31,000
Equity
NOK 356,000
Est. value
NOK 349,000

Financial health · 2025

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

Who owns NANSETGATA 23 AS?

ODD ARILD BJØRNEVIK
NANSETGATA 23 AS
NOK 527,000 rev. · NOK 31,000 profit

NANSETGATA 23 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NANSETGATA 23 AS

Who owns NANSETGATA 23 AS?

ODD ARILD BJØRNEVIK is the largest registered owner, with 50.0%.

What is the revenue of NANSETGATA 23 AS?

NANSETGATA 23 AS had revenue of NOK 527,000 in 2025.

Who is the general manager of NANSETGATA 23 AS?

Karin Østensen is registered as general manager of NANSETGATA 23 AS.

Where is NANSETGATA 23 AS based?

NANSETGATA 23 AS has its business address in Larvik.

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.