BIZTRAC BETA
Buying and selling of own real estate

LÅVEVEIEN 70 NÆRING AS

Org. no. 926926160 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −29,000
Equity NOK 28,000
Incorporated 2021
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−29k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LÅVEVEIEN 70 NÆRING AS is registered as a limited company in Oslo, Oslo with organisation number 926926160. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Erverve, utvikle, drive og avhende fast eiendom, samt all annen naturlig tilhørende virksomhet. Selskapet kan eie aksjer i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −29,000
Equity
NOK 28,000
Est. value
NOK 25,000

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LÅVEVEIEN 70 NÆRING AS?

LÅVEVEIEN 70 HOLDING AS
LÅVEVEIEN 70 NÆRING AS
· NOK −29,000 profit

LÅVEVEIEN 70 NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LÅVEVEIEN 70 NÆRING AS

Who owns LÅVEVEIEN 70 NÆRING AS?

LÅVEVEIEN 70 HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of LÅVEVEIEN 70 NÆRING AS?

Trygve Johan Ulvig Kiær is registered as general manager of LÅVEVEIEN 70 NÆRING AS.

Where is LÅVEVEIEN 70 NÆRING AS based?

LÅVEVEIEN 70 NÆRING 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 15.06.2026.

Report a problem

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