BIZTRAC BETA
Rental and operating of own or leased real estate

BJØDNABEEN 16 AS

Org. no. 931541692 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.2m
Operating profit NOK 3.3m
Equity NOK 15.7m
Incorporated 2023
Share capital NOK 200,000

Signals

1 flags
  • Nylig endring 2026-07-03 Adresseendring registrert 2026-07-03.

BJØDNABEEN 16 AS is registered as a limited company in Stavanger, Rogaland with organisation number 931541692. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 100000 shares. The company's stated purpose is: “Å eie og leie ut egen eiendom og det som står i herved forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK 3.3m in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
Operating profit
NOK 3.3m
Equity
NOK 15.7m
Est. value
NOK 17.6m

Financial health · 2025

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

Who owns BJØDNABEEN 16 AS?

LUND EIENDOM HOLDING AS
BJØDNABEEN 16 AS
NOK 5.2m rev. · NOK 3.3m profit

BJØDNABEEN 16 AS has 2 registered shareholders:

All shareholders and roles →

Group structure

BJØDNABEEN 16 AS er morselskap for 1 datterselskap:

Frequently asked questions about BJØDNABEEN 16 AS

Who owns BJØDNABEEN 16 AS?

LUND EIENDOM HOLDING AS is the largest registered owner, with 90.0%.

What is the revenue of BJØDNABEEN 16 AS?

BJØDNABEEN 16 AS had revenue of NOK 5.2m in 2025.

Who is the general manager of BJØDNABEEN 16 AS?

Ola Soppeland is registered as general manager of BJØDNABEEN 16 AS.

Where is BJØDNABEEN 16 AS based?

BJØDNABEEN 16 AS has its business address in Stavanger.

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.