BIZTRAC BETA
Rental and operating of own or leased real estate

LAACHESÆTER AS

Org. no. 923852212 Limited company (AS) Ås Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 59,000
Equity NOK 496,000
Incorporated 2019
Share capital NOK 30,000

LAACHESÆTER AS is registered as a limited company in Ås, Akershus with organisation number 923852212. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fotografering og naturlig tilhørende virksomhet relatert til dette, prosjektledelse og konsulentoppdrag. Drift og utleie av fast eiendom og naturlig tilhørende virksomhet relatert til dette, herunder også gjennom investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 59,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 59,000
Equity
NOK 496,000
Est. value
NOK 519,000

Financial health · 2024

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

Who owns LAACHESÆTER AS?

KARINE LAACHESÆTER
LAACHESÆTER AS
NOK 1.3m rev. · NOK 59,000 profit

LAACHESÆTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAACHESÆTER AS

Who owns LAACHESÆTER AS?

KARINE LAACHESÆTER is the largest registered owner, with 100.0%.

What is the revenue of LAACHESÆTER AS?

LAACHESÆTER AS had revenue of NOK 1.3m in 2024.

Who is the general manager of LAACHESÆTER AS?

Karine Laachesæter is registered as general manager of LAACHESÆTER AS.

Where is LAACHESÆTER AS based?

LAACHESÆTER AS has its business address in Ås.

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.