biztrac. BETA
COMPANY REGISTER PROFILE
991255257 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

VINJESGATE 10 AS

Org. no. 991255257 Limited company (AS) Drammen Incorporated 2007 Active
Revenue 2025 NOK 1.2m
Operating profit NOK 592,000
Equity NOK 300,000
Incorporated 2007
Share capital NOK 300,000

VINJESGATE 10 AS is registered as a limited company in Drammen, Buskerud with organisation number 991255257. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, investering i fast eiendom, aksjer og andre verdipapirer med dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 592,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▲ +1 %
Operating profit
NOK 592,000
▼ −5 %
Equity
NOK 300,000
▼ −3 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
0.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
18.0%
Very good
Return on total assets
Solidity
8.9%
Weak
Equity as a share of total capital

Who owns VINJESGATE 10 AS?

VINJESGATE 10 AS
NOK 1.2m rev. · NOK 592,000 profit

VINJESGATE 10 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINJESGATE 10 AS

Who owns VINJESGATE 10 AS?

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

What is the revenue of VINJESGATE 10 AS?

VINJESGATE 10 AS had revenue of NOK 1.2m in 2025.

Who is the general manager of VINJESGATE 10 AS?

Kjersti Solvoll Jølberg is registered as general manager of VINJESGATE 10 AS.

Where is VINJESGATE 10 AS based?

VINJESGATE 10 AS has its business address in Drammen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.