BIZTRAC BETA
COMPANY REGISTER PROFILE
998890950 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

SYRETÅRNET 37 AS

Org. no. 998890950 Limited company (AS) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 715,000
Operating profit NOK 165,000
Equity NOK 5.7m
Incorporated 2012
Share capital NOK 60,000

SYRETÅRNET 37 AS is registered as a limited company in Asker, Akershus with organisation number 998890950. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 715,000 in revenue and NOK 165,000 in operating profit.

Key figures · 2024

Revenue
NOK 715,000
Operating profit
NOK 165,000
Equity
NOK 5.7m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns SYRETÅRNET 37 AS?

DRENGSRUD HERREGÅRD DA
SYRETÅRNET 37 AS
NOK 715,000 rev. · NOK 165,000 profit

SYRETÅRNET 37 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYRETÅRNET 37 AS

Who owns SYRETÅRNET 37 AS?

DRENGSRUD HERREGÅRD DA is the largest registered owner, with 100.0%.

What is the revenue of SYRETÅRNET 37 AS?

SYRETÅRNET 37 AS had revenue of NOK 715,000 in 2024.

Who is the general manager of SYRETÅRNET 37 AS?

Ellen Drengsrud is registered as general manager of SYRETÅRNET 37 AS.

Where is SYRETÅRNET 37 AS based?

SYRETÅRNET 37 AS has its business address in Asker.

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.