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

NYE TORSHOVBYGG AS

Org. no. 920814395 Limited company (AS) Oslo Incorporated 2018 Active
Revenue 2025 NOK 70.1m
Operating profit NOK 3.4m
Equity NOK 5.5m
Incorporated 2018
Share capital NOK 60,000

NYE TORSHOVBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 920814395. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 300 shares. The company's stated purpose is: “Utvikling og forvaltning av fast eiendom og alt som naturlig står i forbindelse med dette, herunder direkte og indirekte investeringer i foretak som driver slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 70.1m in revenue and NOK 3.4m in operating profit.

Key figures · 2025

Revenue
NOK 70.1m
▼ −57 %
Operating profit
NOK 3.4m
▲ +478 %
Equity
NOK 5.5m
▼ −96 %
Est. value
NOK 9.8m

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
4.5%
Weak
Return on total assets
Solidity
34.3%
Good
Equity as a share of total capital

Who owns NYE TORSHOVBYGG AS?

NYE TORSHOVBYGG AS
NOK 70.1m rev. · NOK 3.4m profit

NYE TORSHOVBYGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NYE TORSHOVBYGG AS er morselskap for 11 datterselskaper:

Frequently asked questions about NYE TORSHOVBYGG AS

Who owns NYE TORSHOVBYGG AS?

USBL UTBYGGING AS is the largest registered owner, with 100.0%.

What is the revenue of NYE TORSHOVBYGG AS?

NYE TORSHOVBYGG AS had revenue of NOK 70.1m in 2025.

Where is NYE TORSHOVBYGG AS based?

NYE TORSHOVBYGG 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.