BIZTRAC BETA
Construction of residential and non-residential buildings

AT RIGG BYGG AS

Org. no. 917395489 Limited company (AS) Lørenskog Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 24.4m
Operating profit NOK −213,000
Equity NOK 1.0m
Incorporated 2016
Employees 31
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−213k kr).

AT RIGG BYGG AS is registered as a limited company in Lørenskog, Akershus with organisation number 917395489. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016 and has 31 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Diverse byggetjenester. Import og eksport av byggevarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 24.4m in revenue and NOK −213,000 in operating profit.

Key figures · 2025

Revenue
NOK 24.4m
Operating profit
NOK −213,000
Equity
NOK 1.0m
Est. value
NOK 8.9m

Financial health · 2025

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.9%
Satisfactory
Equity as a share of total capital

Who owns AT RIGG BYGG AS?

ADAM STANISLAW TLALKA
AT RIGG BYGG AS
NOK 24.4m rev. · NOK −213,000 profit

AT RIGG BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AT RIGG BYGG AS

Who owns AT RIGG BYGG AS?

ADAM STANISLAW TLALKA is the largest registered owner, with 100.0%.

What is the revenue of AT RIGG BYGG AS?

AT RIGG BYGG AS had revenue of NOK 24.4m in 2025.

Who is the general manager of AT RIGG BYGG AS?

Adam Stanislaw Tlalka is registered as general manager of AT RIGG BYGG AS.

Where is AT RIGG BYGG AS based?

AT RIGG BYGG AS has its business address in Finstadjordet.

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.