BIZTRAC BETA
COMPANY REGISTER PROFILE
917454574 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

BILLINGSTADSLETTA 19 AS

Org. no. 917454574 Limited company (AS) Asker Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 14.7m
Operating profit NOK 8.4m
Equity NOK 17.1m
Incorporated 2016
Share capital NOK 30,000

BILLINGSTADSLETTA 19 AS is registered as a limited company in Asker, Akershus with organisation number 917454574. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utleie av egen fast eiendom, samt all annen naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.7m in revenue and NOK 8.4m in operating profit.

Key figures · 2025

Revenue
NOK 14.7m
Operating profit
NOK 8.4m
Equity
NOK 17.1m
Est. value
NOK 26.3m

Financial health · 2025

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.2%
Good
Equity as a share of total capital

Who owns BILLINGSTADSLETTA 19 AS?

BILLINGSTADSLETTA 19 AS
NOK 14.7m rev. · NOK 8.4m profit

BILLINGSTADSLETTA 19 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILLINGSTADSLETTA 19 AS

Who owns BILLINGSTADSLETTA 19 AS?

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

What is the revenue of BILLINGSTADSLETTA 19 AS?

BILLINGSTADSLETTA 19 AS had revenue of NOK 14.7m in 2025.

Who is the general manager of BILLINGSTADSLETTA 19 AS?

Joakim Hereng is registered as general manager of BILLINGSTADSLETTA 19 AS.

Where is BILLINGSTADSLETTA 19 AS based?

BILLINGSTADSLETTA 19 AS has its business address in Billingstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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