BIZTRAC BETA
Business and other management consultancy activities

KAMMERHERRELØKKA NÆRING B1 AS

Org. no. 991502734 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 7.7m
Operating profit NOK 3.7m
Equity NOK 1.3m
Incorporated 2007
Share capital NOK 200,000

Signals

1 flags
  • Nylig endring 2026-06-15 Adresseendring registrert 2026-06-15.

KAMMERHERRELØKKA NÆRING B1 AS is registered as a limited company in Oslo, Oslo with organisation number 991502734. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2007. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Virksomhet innenfor utvikling og investering i andre selskaper og alt som står i forbindelse med de forannevnte virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.7m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 7.7m
Operating profit
NOK 3.7m
Equity
NOK 1.3m
Est. value
NOK 11.1m

Financial health · 2024

Liquidity
23.80
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.4%
Not satisfactory
Equity as a share of total capital

Who owns KAMMERHERRELØKKA NÆRING B1 AS?

OFFENTLIG EIENDOM AS
KAMMERHERRELØKKA NÆRING B1 AS
NOK 7.7m rev. · NOK 3.7m profit

KAMMERHERRELØKKA NÆRING B1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAMMERHERRELØKKA NÆRING B1 AS

Who owns KAMMERHERRELØKKA NÆRING B1 AS?

OFFENTLIG EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KAMMERHERRELØKKA NÆRING B1 AS?

KAMMERHERRELØKKA NÆRING B1 AS had revenue of NOK 7.7m in 2024.

Where is KAMMERHERRELØKKA NÆRING B1 AS based?

KAMMERHERRELØKKA NÆRING B1 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.