BIZTRAC BETA
COMPANY REGISTER PROFILE
913130065 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Construction of residential and non-residential buildings

TRYGG-BYGG AS

Org. no. 913130065 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 199,000
Equity NOK −599,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−599k kr).

TRYGG-BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 913130065. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Byggvirksomhet og eiendom”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 199,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 199,000
Equity
NOK −599,000
Est. value
NOK 955,000

Financial health · 2025

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-94.8%
Weak
Equity as a share of total capital

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

Who owns TRYGG-BYGG AS?

BESART SHABANI
TRYGG-BYGG AS
NOK 2.6m rev. · NOK 199,000 profit

TRYGG-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYGG-BYGG AS

Who owns TRYGG-BYGG AS?

BESART SHABANI is the largest registered owner, with 100.0%.

What is the revenue of TRYGG-BYGG AS?

TRYGG-BYGG AS had revenue of NOK 2.6m in 2025.

Who is the general manager of TRYGG-BYGG AS?

Besart Shabani is registered as general manager of TRYGG-BYGG AS.

Where is TRYGG-BYGG AS based?

TRYGG-BYGG 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.