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

2T ENTREPRENØR AS

Org. no. 932234009 Limited company (AS) Aurskog-Høland Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 256,000
Equity NOK 1.2m
Incorporated 2023
Employees 6
Share capital NOK 30,000

2T ENTREPRENØR AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 932234009. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Grunnarbeid, byggetjenester og anleggsleverandører, snekkerarbeid, asfaltarbeid og alt relatert til det.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 256,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
▲ +81 %
Operating profit
NOK 256,000
▼ −75 %
Equity
NOK 1.2m
▲ +16 %
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
2.17
Very good
Current assets ÷ current liabilities
Profitability
12.8%
Good
Return on total assets
Solidity
48.0%
Very good
Equity as a share of total capital

Who owns 2T ENTREPRENØR AS?

2T ENTREPRENØR AS
NOK 5.5m rev. · NOK 256,000 profit

2T ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 2T ENTREPRENØR AS

Who owns 2T ENTREPRENØR AS?

2T INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of 2T ENTREPRENØR AS?

2T ENTREPRENØR AS had revenue of NOK 5.5m in 2025.

Who is the general manager of 2T ENTREPRENØR AS?

Ramunas Goveika is registered as general manager of 2T ENTREPRENØR AS.

Where is 2T ENTREPRENØR AS based?

2T ENTREPRENØR AS has its business address in Bjørkelangen.

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.