biztrac. BETA
COMPANY REGISTER PROFILE
999100821 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
All other professional, scientific and technical activities n.e.c.

WEBERGSLØKKA AS

Org. no. 999100821 Limited company (AS) Oslo Incorporated 2012 Active
Revenue 2025 NOK 1.0m
Operating profit NOK −121,000
Equity NOK −4.2m
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,2 mill kr).

WEBERGSLØKKA AS is registered as a limited company in Oslo, Oslo with organisation number 999100821. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering og utvikling av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −121,000 in operating profit.

Former names: LANDBRUKSUTVIKLING AS, SARA INVEST AS

Key figures · 2025

Revenue
NOK 1.0m
▲ +57 %
Operating profit
NOK −121,000
▲ +82 %
Equity
NOK −4.2m
▼ −116 %

Financial health · 2025

Liquidity
10.29
Very good
Current assets ÷ current liabilities
Profitability
-0.4%
Not satisfactory
Return on total assets
Solidity
-17.7%
Weak
Equity as a share of total capital

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

Who owns WEBERGSLØKKA AS?

WEBERGSLØKKA AS
NOK 1.0m rev. · NOK −121,000 profit

WEBERGSLØKKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WEBERGSLØKKA AS

Who owns WEBERGSLØKKA AS?

SANS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of WEBERGSLØKKA AS?

WEBERGSLØKKA AS had revenue of NOK 1.0m in 2025.

Where is WEBERGSLØKKA AS based?

WEBERGSLØKKA 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.