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

STASJONSVEIEN 19 B AS

Org. no. 985228604 Limited company (AS) Oslo Incorporated 2002 Active
Revenue 2025 NOK 8.3m
Operating profit NOK 8.2m
Equity NOK 117,000
Incorporated 2002
Share capital NOK 100,000

STASJONSVEIEN 19 B AS is registered as a limited company in Oslo, Oslo with organisation number 985228604. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og utleie av eiendommen.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.3m in revenue and NOK 8.2m in operating profit.

Key figures · 2025

Revenue
NOK 8.3m
▲ +3207 %
Operating profit
NOK 8.2m
▲ +4020 %
Equity
NOK 117,000
▼ −89 %
Est. value
NOK 10.2m

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
146.7%
Very good
Return on total assets
Solidity
1.2%
Not satisfactory
Equity as a share of total capital

Who owns STASJONSVEIEN 19 B AS?

STASJONSVEIEN 19 B AS
NOK 8.3m rev. · NOK 8.2m profit

STASJONSVEIEN 19 B AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STASJONSVEIEN 19 B AS

Who owns STASJONSVEIEN 19 B AS?

Evelyn Catharina Advocaat Francke is the largest registered owner, with 99.0%.

What is the revenue of STASJONSVEIEN 19 B AS?

STASJONSVEIEN 19 B AS had revenue of NOK 8.3m in 2025.

Who is the general manager of STASJONSVEIEN 19 B AS?

Evelyn Catharina Advocaat Francke is registered as general manager of STASJONSVEIEN 19 B AS.

Where is STASJONSVEIEN 19 B AS based?

STASJONSVEIEN 19 B 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 03.10.2026.

Report a problem

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