biztrac. BETA
COMPANY REGISTER PROFILE
920254055 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Site preparation

BT ANLEGG AS

Org. no. 920254055 Limited company (AS) Lillestrøm Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 11.7m
Operating profit NOK −508,000
Equity NOK −93,000
Incorporated 2017
Employees 7
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−93k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−508k kr).

BT ANLEGG AS is registered as a limited company in Lillestrøm, Akershus with organisation number 920254055. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Maskinentreprenør, graving og riving, utleie av maskiner.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.7m in revenue and NOK −508,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.7m
▼ −7 %
Operating profit
NOK −508,000
▼ −613 %
Equity
NOK −93,000
▼ −118 %

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
-8.3%
Not satisfactory
Return on total assets
Solidity
-1.7%
Weak
Equity as a share of total capital

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

Who owns BT ANLEGG AS?

BT ANLEGG AS
NOK 11.7m rev. · NOK −508,000 profit

BT ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BT ANLEGG AS

Who owns BT ANLEGG AS?

Bjørn Arild Thomassen is the largest registered owner, with 100.0%.

What is the revenue of BT ANLEGG AS?

BT ANLEGG AS had revenue of NOK 11.7m in 2025.

Where is BT ANLEGG AS based?

BT ANLEGG AS has its business address in Skedsmokorset.

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.