BIZTRAC BETA
Rental and operating of own or leased real estate

BRYNSENGVEIEN 2 AS

Org. no. 988403059 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 12.1m
Operating profit NOK 5.8m
Equity NOK 20.5m
Incorporated 2005
Share capital NOK 10.0m

Signals

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

BRYNSENGVEIEN 2 AS is registered as a limited company in Oslo, Oslo with organisation number 988403059. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 10.0m, divided into 10000 shares. The company's stated purpose is: “Investeringer i og forvaltning av fast eiendom, samt tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.1m in revenue and NOK 5.8m in operating profit.

Key figures · 2024

Revenue
NOK 12.1m
Operating profit
NOK 5.8m
Equity
NOK 20.5m
Est. value
NOK 29.2m

Financial health · 2024

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

Who owns BRYNSENGVEIEN 2 AS?

BRYN EIENDOM AS
BRYNSENGVEIEN 2 AS
NOK 12.1m rev. · NOK 5.8m profit

BRYNSENGVEIEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRYNSENGVEIEN 2 AS

Who owns BRYNSENGVEIEN 2 AS?

BRYN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BRYNSENGVEIEN 2 AS?

BRYNSENGVEIEN 2 AS had revenue of NOK 12.1m in 2024.

Who is the general manager of BRYNSENGVEIEN 2 AS?

Jan Ivar Nygaard is registered as general manager of BRYNSENGVEIEN 2 AS.

Where is BRYNSENGVEIEN 2 AS based?

BRYNSENGVEIEN 2 AS has its business address in Oslo.

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.