biztrac. BETA
COMPANY REGISTER PROFILE
898776182 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

LA SÅDA AS

Org. no. 898776182 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK 80,000
Equity NOK −1.9m
Incorporated 2012
Employees 11
Share capital NOK 30,000

Signals

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

LA SÅDA AS is registered as a limited company in Oslo, Oslo with organisation number 898776182. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av restaurant, kafe og catering cateringvirksomhet, samt salg av andre varer som naturlig tilhører driften.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK 80,000 in operating profit.

Former names: K4K - KVINNER FOR KVINNER - AS

Key figures · 2025

Revenue
NOK 4.5m
▲ +15 %
Operating profit
NOK 80,000
▲ +4034 %
Equity
NOK −1.9m
▼ −2 %
Est. value
NOK 394,000

Financial health · 2025

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

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

Who owns LA SÅDA AS?

LA SÅDA AS
NOK 4.5m rev. · NOK 80,000 profit

LA SÅDA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LA SÅDA AS

Who owns LA SÅDA AS?

NESTEN SOM HJEMME HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LA SÅDA AS?

LA SÅDA AS had revenue of NOK 4.5m in 2025.

Where is LA SÅDA AS based?

LA SÅDA 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.