BIZTRAC BETA
Washing and cleaning of textile and fur products

OT SERVICE AS

Org. no. 826017392 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 130,000
Equity NOK 320,000
Incorporated 2020
Share capital NOK 30,000

OT SERVICE AS is registered as a limited company in Oslo, Oslo with organisation number 826017392. The business is classified under washing and cleaning of textile and fur products (NACE 96.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bedriftsutvikling, forretningsdrift og investeringer - herunder deltakelse i eller med andre selskaper. Tjenesteyting i tilknytning til tekstiler. Herunder drift av vaskerier og renserier, samt drive handel og utleie av tekstiler og tilknyttede varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 130,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 130,000
Equity
NOK 320,000
Est. value
NOK 502,000

Financial health · 2025

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

Who owns OT SERVICE AS?

ESPEN TANGEN FOLKØY
OT SERVICE AS
NOK 3.5m rev. · NOK 130,000 profit

OT SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OT SERVICE AS

Who owns OT SERVICE AS?

ESPEN TANGEN FOLKØY is the largest registered owner, with 100.0%.

What is the revenue of OT SERVICE AS?

OT SERVICE AS had revenue of NOK 3.5m in 2025.

Who is the general manager of OT SERVICE AS?

Espen Tangen Folkøy is registered as general manager of OT SERVICE AS.

Where is OT SERVICE AS based?

OT SERVICE 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.