BIZTRAC BETA
Buying and selling of own real estate

NEDRE TVERRGATE 3 NÆRING AS

Org. no. 929880633 Limited company (AS) Lier Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 131,000
Equity NOK 965,000
Incorporated 2022
Share capital NOK 47,000

Signals

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

NEDRE TVERRGATE 3 NÆRING AS is registered as a limited company in Lier, Buskerud with organisation number 929880633. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 47,000, divided into 1 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 131,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 131,000
Equity
NOK 965,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.6%
Satisfactory
Equity as a share of total capital

Who owns NEDRE TVERRGATE 3 NÆRING AS?

RUBA INVEST AS
NEDRE TVERRGATE 3 NÆRING AS
NOK 1.7m rev. · NOK 131,000 profit

NEDRE TVERRGATE 3 NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEDRE TVERRGATE 3 NÆRING AS

Who owns NEDRE TVERRGATE 3 NÆRING AS?

RUBA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of NEDRE TVERRGATE 3 NÆRING AS?

NEDRE TVERRGATE 3 NÆRING AS had revenue of NOK 1.7m in 2025.

Where is NEDRE TVERRGATE 3 NÆRING AS based?

NEDRE TVERRGATE 3 NÆRING AS has its business address in Lier.

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.