biztrac. BETA
COMPANY REGISTER PROFILE
916175817 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

STANSEVEIEN 31 AS

Org. no. 916175817 Limited company (AS) Oslo Incorporated 1924 Active
Revenue 2025 NOK 3.3m
Operating profit NOK 2.5m
Equity NOK 3.5m
Incorporated 1924
Share capital NOK 240,000

STANSEVEIEN 31 AS is registered as a limited company in Oslo, Oslo with organisation number 916175817. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1924. Registered share capital is NOK 240,000. The company's stated purpose is: “Ervervelse og forvaltning av fast eiendom samt hva som her står i forbindelse. Deltakelse i andre selskaper gjennom aksjebesittelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 2.5m in operating profit.

Former names: AAMODT EIENDOM AS

Key figures · 2025

Revenue
NOK 3.3m
▲ +6 %
Operating profit
NOK 2.5m
▲ +23 %
Equity
NOK 3.5m
▼ −5 %
Est. value
NOK 7.0m

Financial health · 2025

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
27.8%
Very good
Return on total assets
Solidity
29.6%
Good
Equity as a share of total capital

Who owns STANSEVEIEN 31 AS?

STANSEVEIEN 31 AS
NOK 3.3m rev. · NOK 2.5m profit

STANSEVEIEN 31 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STANSEVEIEN 31 AS

Who owns STANSEVEIEN 31 AS?

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

What is the revenue of STANSEVEIEN 31 AS?

STANSEVEIEN 31 AS had revenue of NOK 3.3m in 2025.

Who is the general manager of STANSEVEIEN 31 AS?

Roger Grant Gustavsen is registered as general manager of STANSEVEIEN 31 AS.

Where is STANSEVEIEN 31 AS based?

STANSEVEIEN 31 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.